io.github.f-tiger/agiscorecard-web3-permit
REMOTE · PERMIT.AGISCORECARD.COM
Review declared AI data permissions, expiry and regions; model revenue splits without moving funds.
Available components
Last scanned (15 hours ago)
Scores higher than 63% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Finance and Payments
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 Security69
- 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
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 483 tokens (~60/item across 8 items; 3 tools + 5 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 75% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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.
- 17 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 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.
- 13 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 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 18 Oct 2026 · Probed https://permit.agiscorecard.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=agiscorecard.com | CN=WE1,O=Google Trust Services,C=US | 19 Sept 2026 | 18 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 6b903c36c153d0eb0e1e7fcc4a34e014 |
| SANs: agiscorecard.com, permit.agiscorecard.com, *.permit.agiscorecard.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 insecure
Validation of permit.agiscorecard.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| agiscorecard.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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'none'; script-src 'self'; frame-src 'self'; style-src 'self'; img-src 'self' https://*.agiscorecard.com; connect-src 'self'; base-uri 'none'; form-action 'none'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://permit.agiscorecard.com/mcp | Verified | 200 | |
| http (plaintext) | http://permit.agiscorecard.com/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 →
check_data_permissions Data Permit ~208
Data Permit compares an intended AI use with your recorded grant conditions: region, expiry, revocation and consent status. It calculates a proposed split of received revenue and keeps incompatible shares unallocated. Matching fields does not establish a legal license. No legal opinion, rights verification, consent collection, access enforcement, token issuance or payment. Retrieve permit with fetch or read its example resource to obtain exact inputs. Parameters are processed remotely without application persistence.
| Name | Type | Req | Description |
|---|---|---|---|
| asOf | string | yes | Review date (UTC) (preserve source text; decimal amounts must stay strings) |
| currency | string | yes | Currency (preserve source text; decimal amounts must stay strings) |
| datasets | array | yes | Datasets |
| receivedRevenue | string | yes | Revenue already received (preserve source text; decimal amounts must stay strings) |
| region | string | yes | Region (preserve source text; decimal amounts must stay strings) |
| use | string | yes | Use (preserve source text; decimal amounts must stay strings) |
| Name | Type | Req | Description |
|---|---|---|---|
| citation | object | yes | – |
| evidenceStatus | string | yes | – |
| limitations | string | yes | – |
| officialReferences | array | yes | – |
| processing | string | yes | – |
| report | object | yes | – |
| revision | string | yes | – |
| toolId | string | yes | – |
| version | string | yes | – |
No examples provided.
fetch Read a Web3 method and sources ~49
Retrieve a public tool reference by the ID returned from search. Contains methodology, limits, official source links and fictional worked examples; no user records. Cite the returned canonical URL.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| metadata | object | yes | – |
| text | string | yes | – |
| title | string | yes | – |
| url | string | yes | – |
No examples provided.
search Find a Web3 worksheet ~40
Search this server’s public AI/Web3 tools and citation pages. English and Chinese names supported. Empty query lists the available worksheets.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | – |
No examples provided.
How do I install the io.github.f-tiger/agiscorecard-web3-permit MCP server?
io.github.f-tiger/agiscorecard-web3-permit is a hosted endpoint at https://permit.agiscorecard.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 · permit.agiscorecard.com
claude mcp add --transport http f-tiger-agiscorecard-web3-permit 'https://permit.agiscorecard.com/mcp'
What is the io.github.f-tiger/agiscorecard-web3-permit MCP server?
io.github.f-tiger/agiscorecard-web3-permit is an MCP server listed in the public MCP registry as io.github.f-tiger/agiscorecard-web3-permit. Review declared AI data permissions, expiry and regions; model revenue splits without moving funds. This page covers its hosted endpoint (https://permit.agiscorecard.com/mcp).
Is the io.github.f-tiger/agiscorecard-web3-permit MCP server safe to use?
io.github.f-tiger/agiscorecard-web3-permit scores 72 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 io.github.f-tiger/agiscorecard-web3-permit MCP server expose?
io.github.f-tiger/agiscorecard-web3-permit exposes 3 tools: search, fetch, check_data_permissions. Their descriptions and schemas cost roughly 297 tokens of context every time the server is loaded.
Does the io.github.f-tiger/agiscorecard-web3-permit MCP server require authentication?
No. We connected to io.github.f-tiger/agiscorecard-web3-permit without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.f-tiger/agiscorecard-web3-permit MCP server still maintained?
io.github.f-tiger/agiscorecard-web3-permit 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.