com.pythonanywhere.paynemuse/agent-eligibility
REMOTE · PAYNEMUSE.PYTHONANYWHERE.COM
Deterministic eligibility scoring for AI agents: CLEAR/HOLD/FAIL verdicts, published weights.
Available components
Last scanned (21 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 401 tokens (~66/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 −1
- Schema quality: 56 → 66 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- New tool “check_counterparty” functional
- New tool “check_sanctions” functional
- New tool “check_vat” functional
- 13 Oct 26 59
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 18 Oct 2026 · Probed https://paynemuse.pythonanywhere.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.pythonanywhere.com | CN=YE2,O=Let's Encrypt,C=US | 21 Sept 2026 | 20 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5f42705e4274c8eb2b24a997abb8ecba729 |
| SANs: *.pythonanywhere.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of paynemuse.pythonanywhere.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| pythonanywhere.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://paynemuse.pythonanywhere.com/mcp | Verified | 200 | |
| http (plaintext) | http://paynemuse.pythonanywhere.com/mcp | HTTPS enforced | 302 | https://paynemuse.pythonanywhere.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_counterparty ~79
Counterparty due-diligence verdict: sanctions screening plus a VAT registration check (when vat_number is given) composed into CLEAR / HOLD / FAIL with both component results. Mirrors the paid HTTP endpoint POST /api/check/counterparty.
| Name | Type | Req | Description |
|---|---|---|---|
| country_code | string | – | – |
| name | string | yes | – |
| vat_number | string | – | – |
No output schema declared.
No examples provided.
check_sanctions ~82
Screen a person or entity name against the OFAC SDN and EU consolidated (FSD) sanctions lists. Returns scored matches (name, list, program, type, score), the list versions used, and checked_at. Mirrors the paid HTTP endpoint POST /api/check/sanctions.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| type | string | – | – |
No output schema declared.
No examples provided.
check_vat ~71
Check an EU VAT number against the official VIES register. Returns valid (bool), the registered name and address, the VIES request identifier, source and checked_at. Mirrors the paid HTTP endpoint POST /api/check/vat.
| Name | Type | Req | Description |
|---|---|---|---|
| country_code | string | yes | – |
| vat_number | string | yes | – |
No output schema declared.
No examples provided.
evaluate_eligibility ~88
Score one (agent, task) pair. Returns the scorer's full result dict as JSON text: decision (CLEAR/HOLD/FAIL), score 0-100, confidence, reasons, next_action, plus evaluation metadata. Unknown (null) evidence counts as unverified.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | – | yes | – |
| required_capabilities | array | yes | – |
| task | string | yes | – |
No output schema declared.
No examples provided.
get_scoring_table ~44
Return the v1.0.0 deduction table, decision bands, confidence rules, and rules version as JSON, so a client can display the published rules.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_paid_services ~37
List the paid x402 services offered by Payne Machine Foundry (prices, endpoints, how to buy). The MCP tools themselves are free.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the com.pythonanywhere.paynemuse/agent-eligibility MCP server?
com.pythonanywhere.paynemuse/agent-eligibility is a hosted endpoint at https://paynemuse.pythonanywhere.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · paynemuse.pythonanywhere.com
claude mcp add --transport http com-pythonanywhere-paynemuse-agent-eligibility 'https://paynemuse.pythonanywhere.com/mcp'
What is the com.pythonanywhere.paynemuse/agent-eligibility MCP server?
com.pythonanywhere.paynemuse/agent-eligibility is an MCP server listed in the public MCP registry as com.pythonanywhere.paynemuse/agent-eligibility. Deterministic eligibility scoring for AI agents: CLEAR/HOLD/FAIL verdicts, published weights. This page covers its hosted endpoint (https://paynemuse.pythonanywhere.com/mcp).
Is the com.pythonanywhere.paynemuse/agent-eligibility MCP server safe to use?
com.pythonanywhere.paynemuse/agent-eligibility scores 60 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.pythonanywhere.paynemuse/agent-eligibility MCP server expose?
com.pythonanywhere.paynemuse/agent-eligibility exposes 6 tools: evaluate_eligibility, get_scoring_table, list_paid_services, check_vat, check_sanctions, check_counterparty. Their descriptions and schemas cost roughly 401 tokens of context every time the server is loaded.
Does the com.pythonanywhere.paynemuse/agent-eligibility MCP server require authentication?
No. We connected to com.pythonanywhere.paynemuse/agent-eligibility without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.pythonanywhere.paynemuse/agent-eligibility MCP server still maintained?
com.pythonanywhere.paynemuse/agent-eligibility is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.