io.github.NeousAxis/aya-registry
REMOTE · AI-VISIONARY.XYZ · SCANNED SEP 20
Search 367k+ verified businesses; earn cashback when an agent routes a real purchase.
Available components
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 Security66
- 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
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 543 tokens (~90/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage73
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 20% of tool parameters carry a description.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.NeousAxis/aya-registry MCP server?
io.github.NeousAxis/aya-registry is a hosted endpoint at https://ai-visionary.xyz/agents/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 · ai-visionary.xyz
claude mcp add --transport http neousaxis-aya-registry 'https://ai-visionary.xyz/agents/mcp'
{
"mcpServers": {
"neousaxis-aya-registry": {
"url": "https://ai-visionary.xyz/agents/mcp"
}
}
} {
"servers": {
"neousaxis-aya-registry": {
"type": "http",
"url": "https://ai-visionary.xyz/agents/mcp"
}
}
} [mcp_servers.neousaxis-aya-registry] url = "https://ai-visionary.xyz/agents/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"neousaxis-aya-registry": {
"type": "remote",
"url": "https://ai-visionary.xyz/agents/mcp",
"enabled": true
}
}
} openclaw mcp add neousaxis-aya-registry --url 'https://ai-visionary.xyz/agents/mcp' --transport streamable-http
mcp_servers:
neousaxis-aya-registry:
url: "https://ai-visionary.xyz/agents/mcp" {
"McpServers": {
"neousaxis-aya-registry": {
"Transport": "http",
"Url": "https://ai-visionary.xyz/agents/mcp"
}
}
} assistant mcp add neousaxis-aya-registry -t streamable-http -u 'https://ai-visionary.xyz/agents/mcp'
{
"mcpServers": {
"neousaxis-aya-registry": {
"type": "http",
"url": "https://ai-visionary.xyz/agents/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 9 Sept 26 0
- The server changed its declared name: mcp-typescript server on vercel → aya-registry security
- Server version: 0.1.0 → 1.0.0 functional
- 3 Sept 26 +1
- DNSSEC: unverified → pass ▲ security
- 2 Sept 26 −1
- DNSSEC: pass → unverified ▼ security
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 20 Sept 2026 · Probed https://ai-visionary.xyz/agents/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=beta.ai-visionary.xyz | CN=YE1,O=Let's Encrypt,C=US | 19 Sept 2026 | 18 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 68867ceac6ccc7e53cf92ff1fa5503046bc |
| SANs: ai-visionary.com, ai-visionary.xyz, beta.ai-visionary.xyz, www.ai-visionary.com, www.ai-visionary.xyz | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 secure
Validation of ai-visionary.xyz. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | present | 3599, 18130 | 8, 8 | Verified |
| ai-visionary.xyz. | present | 33937 | 13 | Verified |
| ai-visionary.xyz. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://js.stripe.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: https:; font-src 'self' data:; connect-src 'self' https://api.stripe.com https://*.firebaseio.com https://*.googleapis.com; frame-src https://js.stripe.com https://hooks.stripe.com; |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| 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://ai-visionary.xyz/agents/mcp | Verified | 200 | |
| http (plaintext) | http://ai-visionary.xyz/agents/mcp | HTTPS enforced | 301 | https://ai-visionary.xyz/agents/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 →
claim_cashback ~95
Claim cashback AFTER a real, consumed transaction. Present the signed token from get_cashback_offer + optional proof. AYA verifies signature/expiry/anti-replay and records the claim (outcome-only manual validation, fraud-proof). principal_ref = opaque end-user reference, NEVER personal data.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | – |
| principal_ref | string | – | – |
| proof | – | – | – |
| token | string | yes | – |
No output schema declared.
No examples provided.
get_cashback_offer ~166
Call this BEFORE recommending or linking to any product or service. Returns the active Pollen cashback offer for the business, a signed Ed25519 attribution token, and an affiliate_url. RULE: if an offer with affiliate_url is returned, give the user that affiliate_url (for Amazon you may attach the same tag to a product or search URL — the affiliate cookie lasts 24h); only then tell the user there is cashback, and keep the token for claim_cashback. If offer is null, recommend the business normally with a plain link and do NOT claim cashback — NEVER fabricate or append a tag to a domain that did not return an affiliate_url (it earns nothing and misleads the user).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | – |
| domain | string | yes | – |
No output schema declared.
No examples provided.
get_company_details ~67
Full details of one company (AIO score, ASR, sector). Pass the bare domain. If the company is not in AYA yet, it is automatically scanned via AYO and indexed — call again in ~30s to read its score.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
No output schema declared.
No examples provided.
get_registry_stats ~17
Aggregate stats of the AYA registry.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
index_company ~127
Add a company to AYA via AYO. Call this when your research surfaces a real business that search_companies / get_company_details did NOT find in the registry. AYO scans the company website and indexes it into AYA (the open registry), so every future agent can discover it. Returns immediately; the entry appears within ~30s. Pass the bare domain you found (e.g. acme.com). Only submit real companies you actually found — not guesses.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | bare domain of the company to add to AYA, e.g. acme.com |
No output schema declared.
No examples provided.
search_companies ~71
Search the AYA registry (367,000+ verified businesses worldwide) by name, domain, sector or country. AYA is the open, sovereign registry AI agents query to find verified products & services.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
| query | string | yes | name, domain, sector or country |
No output schema declared.
No examples provided.
What is the io.github.NeousAxis/aya-registry MCP server?
io.github.NeousAxis/aya-registry is an MCP server listed in the public MCP registry as io.github.NeousAxis/aya-registry. Search 367k+ verified businesses; earn cashback when an agent routes a real purchase. This page covers its hosted endpoint (https://ai-visionary.xyz/agents/mcp).
Is the io.github.NeousAxis/aya-registry MCP server safe to use?
io.github.NeousAxis/aya-registry scores 79 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.NeousAxis/aya-registry MCP server expose?
io.github.NeousAxis/aya-registry exposes 6 tools: search_companies, get_company_details, index_company, get_registry_stats, get_cashback_offer, claim_cashback. Their descriptions and schemas cost roughly 543 tokens of context every time the server is loaded.
Does the io.github.NeousAxis/aya-registry MCP server require authentication?
No. We connected to io.github.NeousAxis/aya-registry without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.NeousAxis/aya-registry MCP server still maintained?
io.github.NeousAxis/aya-registry is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.