Publisher portfolio
throttler300
Explore the MCP servers published by throttler300, with independent connection checks, performance measurements, and setup instructions for each project.
- Listed servers
- 4
Active projects in this portfolio. Deleted and deprecated registry rows are excluded.
- Sampled servers
- 2
Active servers with a recorded connection probe
- Latest probe connected
- 2
Latest stored probe connected. This is not a live guarantee.
- Repositories
- 2
Distinct source repositories linked by the active listings
Portfolio overview
MCP servers
Compare connection status and measurements. Open a server for its tools, check results, and client configuration.
| Server / capability | Last probe | Median latency | Checks passed | Last checked |
|---|---|---|---|---|
Agent Billing Primitives (Dirtsmith) Usage metering, spend cap (reserve before pay), lease lock, semaphore, heartbeat for agents. Free tr | Responded | 83 ms | 12 / 22 | |
work-access-tools Verified product categorization, npm/PyPI package checks, and locks. Free tier; pay after. | Outdated check | 452 ms | 12 / 22 | |
io.github.throttler300/dirtsmith-evidence-quote-check Bind agent citations to admitted source text with spans and optional stale-hash rejection. | Not measured | Not measured | 2 / 6 | Not checked yet |
io.github.throttler300/dirtsmith-record-batch-gate Quarantine invalid or duplicate scraper records before an AI agent writes them downstream. | Not measured | Not measured | 2 / 6 | Not checked yet |
Company & identity
About throttler300
throttler300 publishes MCP servers under the io.github.throttler300 namespace. This namespace is associated with a GitHub login in the MCP Registry.
Namespace verification connects the publisher to its registry identity. It does not certify the security of individual servers.