VALUE Verdicts
REMOTE · VERDICTS.ANAGRAMIC.COM
Safety checks before agents pay, plus world context for any place and time: identity, portals, story
Available components
Last scanned (19 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 4 Nov 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 Security77
- 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 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability58
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 3175 tokens (~244/item across 13 items; 13 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 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 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 1 Nov 26 69
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://verdicts.anagramic.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=anagramic.com | CN=WE1,O=Google Trust Services,C=US | 1 Nov 2026 | 30 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | fbb4a2f1f565cd8a13cb5865437aa5ae |
| SANs: anagramic.com, verdicts.anagramic.com, *.verdicts.anagramic.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of verdicts.anagramic.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| anagramic.com. | present | 2371 | 13 | Verified |
| verdicts.anagramic.com. | Verified address RRset verified with the apex keys |
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://verdicts.anagramic.com/mcp | Verified | 200 | |
| http (plaintext) | http://verdicts.anagramic.com/mcp | HTTPS enforced | 301 | https://verdicts.anagramic.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 →
address_check Payment address check ~222
Before sending crypto: checks an EVM, Solana or Bitcoin address for a valid checksum, the right network, dead/burn/program addresses, a mismatch with the expected payee, and address-poisoning lookalikes of addresses you already trust. Live on-chain lookup: has the address ever been used, is it a wallet, contract or program. Returns pass / caution / fail with reasons. Price: $0.01 USDC per call after 25 free calls per day.
| Name | Type | Req | Description |
|---|---|---|---|
| _payment | string | – | x402 v2 payment: base64 PaymentPayload, as you would send in the PAYMENT-SIGNATURE header. Only needed after the free allowance is used. |
| address | string | yes | The address you are about to pay. |
| expected | string | – | Optional. The address you were told to pay, e.g. from an invoice. |
| known | array | – | Optional. Addresses you have paid or trust before (max 200). GET: comma-separated. |
| network | string | – | Optional. Network you intend to use. |
No output schema declared.
No examples provided.
celestial_earth_projection Global celestial geometry projection ~173
Calculates bounded GeoJSON loci on Earth where each selected major body is at a named angular condition at one UTC minute: AC (rising horizon), MC (upper meridian), DC (setting horizon), or IC (lower meridian). Useful for mapping, visualization, geographic research, and location-aware planning. It returns calculated geometry only, with no interpretation or prediction. Price: $0.02 USDC per call after 25 free calls per day.
| Name | Type | Req | Description |
|---|---|---|---|
| _payment | string | – | x402 v2 payment: base64 PaymentPayload, as you would send in the PAYMENT-SIGNATURE header. Only needed after the free allowance is used. |
| bodies | array | yes | One to four supported major-body names. |
| instantUtc | string | yes | UTC instant, exactly YYYY-MM-DDTHH:mmZ. |
No output schema declared.
No examples provided.
celestial_event_window Celestial angular event window ~231
Searches a bounded UTC range for the requested angular separation between exactly two selected bodies, then refines each detected crossing to the calculator minute. It uses a fixed, owner-operated ephemeris calculator with at most 48 samples and four concurrent requests. Geometry only: no prediction or interpretation. Price: $0.02 USDC per call after 25 free calls per day.
| Name | Type | Req | Description |
|---|---|---|---|
| _payment | string | – | x402 v2 payment: base64 PaymentPayload, as you would send in the PAYMENT-SIGNATURE header. Only needed after the free allowance is used. |
| bodies | array | yes | Exactly two distinct supported body names. |
| endUtc | string | yes | UTC end time, exactly YYYY-MM-DDTHH:mmZ; within seven days. |
| startUtc | string | yes | UTC start time, exactly YYYY-MM-DDTHH:mmZ. |
| stepMinutes | integer | – | Optional sampling interval from 60 to 1440 minutes; default 240. Range and step may not exceed 48 samples. |
| targetDegrees | number | yes | Requested angular separation from 0 to 180 degrees. |
No output schema declared.
No examples provided.
celestial_relations Celestial angular relations ~195
Computes the selected bodies, then returns every pairwise angular separation in degrees. Useful for astronomy, historical reconstruction, rendering, research, and event-planning agents. It returns geometry only, with no predictive or interpretive claims. Price: $0.02 USDC per call after 25 free calls per day.
| Name | Type | Req | Description |
|---|---|---|---|
| _payment | string | – | x402 v2 payment: base64 PaymentPayload, as you would send in the PAYMENT-SIGNATURE header. Only needed after the free allowance is used. |
| bodies | array | yes | Two to 20 supported body names. |
| dateTime | string | yes | Local civil time, exactly YYYY-MM-DDTHH:mm. |
| latitude | number | yes | Observer latitude from -90 to 90. |
| longitude | number | yes | Observer longitude from -180 to 180. |
| timezoneId | string | yes | IANA timezone at the observer, e.g. Pacific/Auckland. |
No output schema declared.
No examples provided.
celestial_state Celestial body state ~201
Computes compact, factual ecliptic positions and motion for selected planets, dwarf planets, or supported minor bodies at an Earth coordinate and local civil time. The result is calculated by the configured ephemeris service; it is not a static lookup or an interpretation. Price: $0.01 USDC per call after 25 free calls per day.
| Name | Type | Req | Description |
|---|---|---|---|
| _payment | string | – | x402 v2 payment: base64 PaymentPayload, as you would send in the PAYMENT-SIGNATURE header. Only needed after the free allowance is used. |
| bodies | array | yes | One to 20 supported body names. |
| dateTime | string | yes | Local civil time, exactly YYYY-MM-DDTHH:mm. |
| latitude | number | yes | Observer latitude from -90 to 90. |
| longitude | number | yes | Observer longitude from -180 to 180. |
| timezoneId | string | yes | IANA timezone at the observer, e.g. Pacific/Auckland. |
No output schema declared.
No examples provided.
contextual_pairing Contextual pairing (places and names, related) ~257
Relates 2-8 world places and up to 8 named entities, deterministically. For each place: its ROAST-78 tile card and element. For every pair: elemental dignity (Golden Dawn rules: strengthening, friendly, opposing or neutral), same suit, lattice step, great-circle distance and initial bearing, and the card of the midpoint tile. Each name is turned into a card sequence with the Anagramic alphabet cipher (A-V = Major Arcana, W-Z = the four Aces), with its dominant element and its dignity with each place. For games, matchmaking, travel stories and multi-location worldbuilding. Includes a receipt hash. Price: $0.02 USDC per call after 25 free calls per day.
| Name | Type | Req | Description |
|---|---|---|---|
| _payment | string | – | x402 v2 payment: base64 PaymentPayload, as you would send in the PAYMENT-SIGNATURE header. Only needed after the free allowance is used. |
| entities | array | – | Optional. Up to 8 names (people, characters, places, brands), max 64 characters each. GET: comma-separated. |
| places | array | yes | 2 to 8 places. GET: flat "lat,lon,lat,lon". |
No output schema declared.
No examples provided.
link_check Phishing link check ~204
Before opening a link or entering credentials: detects lookalike domains (homoglyphs, mixed alphabets, typosquats), brand impersonation in domains and subdomains, hidden destinations (user@host), unsafe schemes, and risky TLDs across 70+ commonly impersonated brands. Live lookups: does the domain exist (DNS) and how old is it (registration date), since most phishing domains are days old. The page itself is never visited. Price: $0.01 USDC per call after 25 free calls per day.
| Name | Type | Req | Description |
|---|---|---|---|
| _payment | string | – | x402 v2 payment: base64 PaymentPayload, as you would send in the PAYMENT-SIGNATURE header. Only needed after the free allowance is used. |
| expectedBrand | string | – | Optional. The brand this link claims to be, e.g. "paypal". Fails if the domain is not official. |
| url | string | yes | The link to check. |
No output schema declared.
No examples provided.
location_context Location context (place + time + sky + story seed) ~294
Everything an agent needs to ground a scene, NPC, quest or prompt in a real place and moment, in one call: the spatial identity with the tile card's full context (meanings, story catalyst, imagery, inspiration prompt, story function and archetype, spread templates, geometry, navigation, correspondences, names in six languages), the time portal with the moment card's full context, the eight neighbouring tiles, approximate sun altitude/daylight and moon phase, and a structured narrative seed ready to hand to a model. No text is generated. Deterministic for a given input and "at", with a receipt hash. Price: $0.02 USDC per call after 25 free calls per day.
| Name | Type | Req | Description |
|---|---|---|---|
| _payment | string | – | x402 v2 payment: base64 PaymentPayload, as you would send in the PAYMENT-SIGNATURE header. Only needed after the free allowance is used. |
| at | string | – | Optional UTC instant, e.g. 2026-11-02T08:30Z. Defaults to now. |
| clock | string | – | Optional. civil (default), solar or utc. |
| latitude | number | yes | Latitude from -90 to 90. |
| longitude | number | yes | Longitude from -180 to 180. |
| timezoneId | string | – | Optional IANA timezone. If omitted, it is looked up from the coordinate (falls back to solar time). |
No output schema declared.
No examples provided.
payment_check x402 payment check ~264
Before you sign an x402 payment to another service: pass the 402 payment request you received and get one verdict on the whole thing. Checks the price against your limit, that the token is real USDC with the right signing name, the payee address (checksum, poisoning lookalikes, on-chain history), whether the request claims a different site than the one you called, and the site itself (lookalike domains, domain age). One call, one price. Price: $0.01 USDC per call after 25 free calls per day.
| Name | Type | Req | Description |
|---|---|---|---|
| _payment | string | – | x402 v2 payment: base64 PaymentPayload, as you would send in the PAYMENT-SIGNATURE header. Only needed after the free allowance is used. |
| knownPayees | array | – | Optional. Payee addresses you have paid before (max 200). GET: comma-separated. |
| maxPrice | string | – | Optional. Your price limit in US dollars, e.g. "0.05". |
| paymentRequired | string|object | yes | The PAYMENT-REQUIRED header value (base64) or the 402 JSON body. GET: base64 only. |
| requestedUrl | string | – | Optional. The URL you called that returned the 402. |
No output schema declared.
No examples provided.
situated_draw Situated draw (verifiable cards for a place and intent) ~353
Draws 1-10 ROAST-78 cards for a world tile and an optional intent, using the public drand beacon (League of Entropy, including Cloudflare; a new BLS-signed value every 3 s). Nobody, including this service, can steer the outcome before the beacon round is published, and anyone can replay it from the receipt (round + tile + intent hash). Positions are named from the place card's own spread template when one exists for that count. Each card includes orientation, meaning, keyword, element, story catalyst and prompt. The intent text is hashed, never stored or returned. Price: $0.01 USDC per call after 25 free calls per day.
| Name | Type | Req | Description |
|---|---|---|---|
| _payment | string | – | x402 v2 payment: base64 PaymentPayload, as you would send in the PAYMENT-SIGNATURE header. Only needed after the free allowance is used. |
| at | string | – | Optional past UTC instant (e.g. 2026-11-02T08:30Z) to draw with the beacon round of that moment. Omit for now. |
| count | integer | – | Optional number of cards, 1 to 10 (default 1). |
| intent | string | – | Optional question or intent (max 500 characters). Only its SHA-256 hash is used and returned. |
| latitude | number | yes | Latitude from -90 to 90. |
| longitude | number | yes | Longitude from -180 to 180. |
| reversals | boolean | – | Optional. Allow reversed cards (default true). |
| round | integer | – | Optional drand round, to replay or verify an earlier draw. Omit for a fresh, unpredictable draw. |
No output schema declared.
No examples provided.
spatial_identity Spatial identity (ROAST-78 world tile) ~239
Gives any Earth coordinate a stable identity: its ~19 m world tile (Web Mercator zoom 21, the Anagramic globe grid), tile bounds and centre, and the deterministic ROAST-78 card that tile holds (Roast-78 character, card, keyword, upright/reversed, element, rune, hieroglyph, I Ching hexagram, math and navigation symbols), plus the eight neighbouring tiles. The same coordinate always returns the same identity, so agents can anchor games, stories, AR scenes and shared worlds to real places. Includes a replayable receipt hash. Price: $0.01 USDC per call after 25 free calls per day.
| Name | Type | Req | Description |
|---|---|---|---|
| _payment | string | – | x402 v2 payment: base64 PaymentPayload, as you would send in the PAYMENT-SIGNATURE header. Only needed after the free allowance is used. |
| includeNeighbours | boolean | – | Optional. Include the eight surrounding tiles (default true). |
| latitude | number | yes | Latitude from -90 to 90 (Web Mercator clamps beyond ±85.05). |
| longitude | number | yes | Longitude from -180 to 180. |
No output schema declared.
No examples provided.
time_portal Time portal (moment card and portal minutes) ~307
Reads the clock at a place and instant and returns the moment card (digit-reduced local HH:MM read as a Major Arcana number), whether this minute is a portal, and the previous and next portal minutes (mirrors, triples, ascending/descending sequences, pi 3:14, phi 6:18, and 12-hour echoes) with exact UTC instants and countdowns. Clock: civil timezone (given, or looked up from the coordinate), mean solar time, or UTC. DST-aware. Same input and "at" always give the same result, with a receipt hash. Price: $0.01 USDC per call after 25 free calls per day.
| Name | Type | Req | Description |
|---|---|---|---|
| _payment | string | – | x402 v2 payment: base64 PaymentPayload, as you would send in the PAYMENT-SIGNATURE header. Only needed after the free allowance is used. |
| at | string | – | Optional UTC instant, e.g. 2026-11-02T08:30Z. Defaults to now. |
| clock | string | – | Optional. civil (default), solar (mean solar time at the longitude) or utc. |
| latitude | number | yes | Latitude from -90 to 90. |
| longitude | number | yes | Longitude from -180 to 180. |
| timezoneId | string | – | Optional IANA timezone, e.g. "Africa/Cairo". If omitted, it is looked up from the coordinate (falls back to solar time). |
No output schema declared.
No examples provided.
x402_preflight Live x402 endpoint preflight ~195
Before paying an x402 service: safely makes one unauthenticated HTTPS request, confirms the endpoint is live and returns a current 402 challenge, then checks its price, USDC token, payee and site. Never signs or settles a payment. HTTPS only; redirects and private/local targets are refused. Price: $0.01 USDC per call after 25 free calls per day.
| Name | Type | Req | Description |
|---|---|---|---|
| _payment | string | – | x402 v2 payment: base64 PaymentPayload, as you would send in the PAYMENT-SIGNATURE header. Only needed after the free allowance is used. |
| knownPayees | array | – | Optional. Payee addresses you have paid before (max 200). GET: comma-separated. |
| maxPrice | string | – | Optional. Your maximum acceptable US-dollar price, e.g. "0.05". |
| url | string | yes | The public HTTPS x402 endpoint to preflight. |
No output schema declared.
No examples provided.
How do I install the VALUE Verdicts MCP server?
VALUE Verdicts is a hosted endpoint at https://verdicts.anagramic.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 · verdicts.anagramic.com
claude mcp add --transport http 5darryl-value-verdicts 'https://verdicts.anagramic.com/mcp'
What is the VALUE Verdicts MCP server?
VALUE Verdicts is an MCP server listed in the public MCP registry as io.github.5Darryl/value-verdicts. Safety checks before agents pay, plus world context for any place and time: identity, portals, story. This page covers its hosted endpoint (https://verdicts.anagramic.com/mcp).
Is the VALUE Verdicts MCP server safe to use?
VALUE Verdicts scores 71 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 VALUE Verdicts MCP server expose?
VALUE Verdicts exposes 13 tools: address_check, link_check, payment_check, x402_preflight, celestial_state, and 8 more. Their descriptions and schemas cost roughly 3,135 tokens of context every time the server is loaded.
Does the VALUE Verdicts MCP server require authentication?
No. We connected to VALUE Verdicts without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the VALUE Verdicts MCP server still maintained?
VALUE Verdicts 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.