369 Meter — pay-per-call APIs for agents (x402)
REMOTE · 369YZ.PYTHONANYWHERE.COM
Pay-per-call APIs for agents: text analysis, game facts, translation QA, hook scoring via x402.
Available components
Last scanned (22 hours ago)
Scores higher than 54% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Entertainment and Games
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 337 tokens (~84/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 28 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.
- 27 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 26 Oct 26 65
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 4 Nov 2026 · Probed https://369yz.pythonanywhere.com/meter/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 369yz.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://369yz.pythonanywhere.com/meter/mcp | Verified | 200 | |
| http (plaintext) | http://369yz.pythonanywhere.com/meter/mcp | Inconclusive | 405 |
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 →
game_facts GameFacts — live game metadata ($0.03/call via x402) ~90
Use this when you need live game metadata from RAWG (release date, ratings, Metacritic, platforms, genres). Pay-per-call: $0.03 USDC on Base via x402 to the REST route POST /v1/game/facts.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Optional, 1-5, default 3 |
| query | string | yes | Game title to look up |
No output schema declared.
No examples provided.
hook_score HookScore — gaming hook scorer ($0.01/call via x402) ~86
Use this when you need a gaming headline or hook scored 0-100 against the 369 team's hook rules. Pay-per-call: $0.01 USDC on Base via x402 to the REST route POST /v1/hook/score.
| Name | Type | Req | Description |
|---|---|---|---|
| headline | string | yes | Headline/hook to score |
| platform | string | – | Optional platform, default 'reels' |
No output schema declared.
No examples provided.
text_analyze TextIntel — text analysis ($0.01/call via x402) ~75
Use this when you need deterministic text analysis (counts, Flesch readability, script mix, top keywords). Pay-per-call: $0.01 USDC on Base via x402 to the REST route POST /v1/text/analyze.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | Text to analyze, up to 20000 chars |
No output schema declared.
No examples provided.
translate_check TranslationCheck — EN<->FA translation QA ($0.02/call via x402) ~86
Use this when you need an EN<->FA translation QA score 0-100 (numbers/entities preserved, script purity, untranslated segments). Pay-per-call: $0.02 USDC on Base via x402 to the REST route POST /v1/translate/check.
| Name | Type | Req | Description |
|---|---|---|---|
| source_text | string | yes | Source text |
| target_text | string | yes | Translated text to check |
No output schema declared.
No examples provided.
How do I install the 369 Meter — pay-per-call APIs for agents (x402) MCP server?
369 Meter — pay-per-call APIs for agents (x402) is a hosted endpoint at https://369yz.pythonanywhere.com/meter/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 · 369yz.pythonanywhere.com
claude mcp add --transport http 369369yz-collab-meter369 'https://369yz.pythonanywhere.com/meter/mcp'
What is the 369 Meter — pay-per-call APIs for agents (x402) MCP server?
369 Meter — pay-per-call APIs for agents (x402) is an MCP server listed in the public MCP registry as io.github.369369yz-collab/meter369. Pay-per-call APIs for agents: text analysis, game facts, translation QA, hook scoring via x402. This page covers its hosted endpoint (https://369yz.pythonanywhere.com/meter/mcp).
Is the 369 Meter — pay-per-call APIs for agents (x402) MCP server safe to use?
369 Meter — pay-per-call APIs for agents (x402) scores 69 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 369 Meter — pay-per-call APIs for agents (x402) MCP server expose?
369 Meter — pay-per-call APIs for agents (x402) exposes 4 tools: text_analyze, hook_score, translate_check, game_facts. Their descriptions and schemas cost roughly 337 tokens of context every time the server is loaded.
Does the 369 Meter — pay-per-call APIs for agents (x402) MCP server require authentication?
No. We connected to 369 Meter — pay-per-call APIs for agents (x402) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the 369 Meter — pay-per-call APIs for agents (x402) MCP server still maintained?
369 Meter — pay-per-call APIs for agents (x402) is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.