AITWIRE
REMOTE · API.AITWIRE.COM · SCANNED SEP 22
Business-published entity records with confirmation dates: look up, page feeds, check claims.
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 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 check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- 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 Usability85
- 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 432 tokens (~72/item across 6 items; 3 tools + 3 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 Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 86% 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 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
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
How do I install the AITWIRE MCP server?
AITWIRE is a hosted endpoint at https://api.aitwire.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 · api.aitwire.com
claude mcp add --transport http com-aitwire-authority 'https://api.aitwire.com/mcp'
{
"mcpServers": {
"com-aitwire-authority": {
"url": "https://api.aitwire.com/mcp"
}
}
} {
"servers": {
"com-aitwire-authority": {
"type": "http",
"url": "https://api.aitwire.com/mcp"
}
}
} [mcp_servers.com-aitwire-authority] url = "https://api.aitwire.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-aitwire-authority": {
"type": "remote",
"url": "https://api.aitwire.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-aitwire-authority --url 'https://api.aitwire.com/mcp' --transport streamable-http
mcp_servers:
com-aitwire-authority:
url: "https://api.aitwire.com/mcp" {
"McpServers": {
"com-aitwire-authority": {
"Transport": "http",
"Url": "https://api.aitwire.com/mcp"
}
}
} assistant mcp add com-aitwire-authority -t streamable-http -u 'https://api.aitwire.com/mcp'
{
"mcpServers": {
"com-aitwire-authority": {
"type": "http",
"url": "https://api.aitwire.com/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.
- 4 Sept 26 +1
- Stability: 0.97 → pass security
- 3 Sept 26 −1
- Stability: pass → 0.97 functional
- 29 Aug 26 +1
- The server rewrote its instructions, which are the text every model session reads 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 0
- Stability: 0.97 → pass security
- 18 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “aitwire_entity_feeds” rewrote its description, which is the text the model reads security
- 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
- 5 Aug 26 0
- HSTS header: unverified → fail ▼ security
- Authorization: unverified → partial ▲ security
- Transport: fail → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Stability: unverified → 0.33 ▲ 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 22 Sept 2026 · Probed https://api.aitwire.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=aitwire.com | CN=WE1,O=Google Trust Services,C=US | 20 Sept 2026 | 19 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 865aedc844f5b7aa13be1dcbff2ed858 |
| SANs: aitwire.com, *.aitwire.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 api.aitwire.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| aitwire.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://api.aitwire.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.aitwire.com/mcp | Served over HTTP | 200 |
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 →
aitwire_entity_feeds ~76
Page an entity's structured feeds on AITWIRE — products, services, articles or locations (tenant_id comes from aitwire_entity_lookup).
| Name | Type | Req | Description |
|---|---|---|---|
| feed_type | string | yes | – |
| limit | number | – | Max items (default 10) |
| tenant_id | string | yes | AITWIRE tenant ID (from lookup) |
No output schema declared.
No examples provided.
aitwire_entity_lookup ~103
Look up a business, brand, organization, person, or website's business-supplied entity record on AITWIRE by domain or name — its confirmed description, feed URLs, and proof counts, each carrying the date it was confirmed. Returns no match for entities that have not published to AITWIRE.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | Domain (e.g. 'example.com') |
| name | string | – | Entity name (e.g. 'AITWIRE') |
No output schema declared.
No examples provided.
aitwire_grounding ~69
Check whether a specific claim matches an entity's business-supplied record on AITWIRE. Returns verified / contradicted / unknown with a confidence score, so you can attribute the result.
| Name | Type | Req | Description |
|---|---|---|---|
| claim | string | yes | Claim to verify |
| entity | string | yes | Entity domain or name |
No output schema declared.
No examples provided.
What is the AITWIRE MCP server?
AITWIRE is an MCP server listed in the public MCP registry as com.aitwire/authority. Business-published entity records with confirmation dates: look up, page feeds, check claims. This page covers its hosted endpoint (https://api.aitwire.com/mcp).
Is the AITWIRE MCP server safe to use?
AITWIRE scores 80 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 AITWIRE MCP server expose?
AITWIRE exposes 3 tools: aitwire_entity_lookup, aitwire_entity_feeds, aitwire_grounding. Their descriptions and schemas cost roughly 248 tokens of context every time the server is loaded.
Does the AITWIRE MCP server require authentication?
No. We connected to AITWIRE without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AITWIRE MCP server still maintained?
AITWIRE is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.