Remote MCP server that meters sampling requests per server, enforces a fail-closed allowance and scope clamp, and issues pre-connect verdicts.
What you can do
Meter a sampling/createMessage request against a per-server ledger with a fail-closed allowance and scope clamp
Get a pre-connect verdict (allow, caution, deny, insufficient data) for one server from your own measured profile
Read your per-server sampling ledger rows
View and tune your allowance and threshold policy
When to use it
Useful when you want to cap and track how much MCP sampling a given server consumes, or check a server's measured profile before connecting to it. Suited to operators who want a policy-based guard rather than ad hoc limits.
Requirements
Runs as a remote streamable HTTP endpoint at textforagents.com; no packages, environment variables or headers are declared. Metering and verdicts beyond the free allowance are billed through x402 payments, so a payment-capable client is needed for paid use.
Before you install
Metering and verdicts are billed: flat coverage first, then per-call x402 charges (0.002 for metered requests, 0.005 for verdicts after the first 100 free ones per operator). Ledger and policy tools expose your operator's data, so treat access to this endpoint as sensitive. Verdicts depend on your own measured profile and may return insufficient data.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.textforagents%2Fsampling-quota-guard/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
Meter one sampling/createMessage request against your per-server ledger + fail-closed allowance + scope clamp. Billed per the pricing sheet (flat coverage, then $0.002 x402). Denied requests never consume allowance.
Parametersserverrequiredrequestrequired
guard_verdict
Pre-connect verdict (ALLOW / CAUTION / DENY / INSUFFICIENT_DATA) for one server from your own measured profile. First 100 verdicts free one time per operator; then $0.005 x402; flat tier covers verdicts.
Parametersserverrequired
guard_ledger
Your per-server sampling ledger rows (your operator only).
Parametersserver
guard_policy
Your allowance + tunable threshold policy.
Takes no parameters.
Version history
2
v1.0.1LatestOct 29, 2026
v1.0.0Oct 22, 2026
Score
83%
83% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.