A remote MCP server that gives an assistant a pre-flight verdict on whether a site permits a given automated task, with evidence and a route.
What you can do
Check a site and task combination for an access verdict (permitted, licensed-only, partner-only, policy-blocked, collateral-blocked or unknown) with supporting evidence and a suggested route
Submit a validated evidence document for fresh assembly, without receiving a verdict
Register a watch on a site and task and get alerted when its access class changes
Generate a site-facing collateral report for a collateral-blocked verdict
Retrieve a stored verdict receipt by its id
When to use it
Use it before an agent starts automated collection or browsing against a site, to check whether that site and task are allowed and what route to take. Also useful when you need to track access-class changes over time or document a blocked case.
Requirements
Remote streamable HTTP endpoint; no packages, environment variables or headers declared. Calls are billed at $0.05 each via x402 payment using the X-PAYMENT header, with one free call per operator and a plan covering cached plus 200 fresh checks per month.
Before you install
Paid per call through x402 with the X-PAYMENT header, so usage can spend money; confirm pricing and plan limits first. Verdicts are advisory and may be unknown, so they should not be treated as legal clearance. Submitting evidence documents and registering watches sends data to the provider.
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%2Fagent-access-door-check/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.
Site-facing collateral report for a COLLATERAL-BLOCKED verdict.
Parameterssiterequiredtaskrequired
get_receipt
Fetch a stored verdict receipt by id.
Parametersreceipt_idrequired
Version history
5
v1.2.6LatestNov 7, 2026
v1.2.2Nov 5, 2026
v1.2.1Nov 4, 2026
v1.2.0Oct 29, 2026
v1.1.1Oct 21, 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.