Skip to content

AITWIRE MCP server

com.aitwire/authorityaitwire.comstreamable-httpv1.0.0Scanned

Business-published entity records with confirmation dates: look up, page feeds, check claims.

3 tools: 2 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 2 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the AITWIRE MCP server can do

The AITWIRE MCP server is published by aitwire.com, a domain the MCP Registry verified. It has 3 tools. It can create or change data (2 tools: aitwire_entity_feeds and aitwire_grounding), but cannot delete data. 1 tool only reads.

1 tool brings in text other people can write (aitwire_entity_lookup).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 12, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

3 tools

Changes things 2Claude Code: ask
  • aitwire_entity_feedsPage an entity's structured feeds on AITWIRE — products, services, articles or locations (tenant_id comes from aitwire_entity_lookup).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Page an entity's structured feeds on AITWIRE — products, services, articles or locations (tenant_id comes from aitwire_entity_lookup).

    Annotations the server declares

    • title: Fetch an entity's structured feeds
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • aitwire_groundingCheck whether a specific claim matches an entity's business-supplied record on AITWIRE.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check a claim against an entity's record
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
Only reads 1Show 1 read-only tool
  • aitwire_entity_lookupLook 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,…Reads text others writeNo findings

    Why it is in this group

    • The name "aitwire_entity_lookup" says "lookup": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "website": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Look up an entity's business record
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:33 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-03-26
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://api.aitwire.com/.well-known/oauth-protected-resource
Authorization servers
https://api.aitwire.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.aitwire.com/mcp: tools/list returned 3 tools to an anonymous client, including aitwire_entity_feeds (write), aitwire_grounding (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http authority https://api.aitwire.com/mcp
claude mcp add --transport http authority https://api.aitwire.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__authority__aitwire_entity_lookup"
    ],
    "ask": [
      "mcp__authority__aitwire_entity_feeds",
      "mcp__authority__aitwire_grounding"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as authority. Review it before you use it.

Capability tags behind 1 rule
  • mcp__authority__aitwire_entity_lookup untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.aitwire/authority/verify?hash=d3f8d23d1263cf303caa6e1151a0ee66f4213a52decb09d3c294afb136c6a47e" | jq -e '.changed == false'

Pinned hash d3f8d23d1263, from Nov 12, 2026, 14:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.aitwire/authority/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.aitwire/authority
[![Anlyon Radar](https://radar.anlyon.com/badge/com.aitwire/authority.svg)](https://radar.anlyon.com/servers/com.aitwire/authority)

Source: MCP Registry. Synced Oct 21, 2026, 17:48 UTC.

AITWIRE MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the AITWIRE MCP server safe?

No scan can promise that. What its definitions show: 3 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the AITWIRE MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the AITWIRE MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the AITWIRE MCP server have?

3 tools: 2 write, 1 read. aitwire_entity_feeds, aitwire_grounding and aitwire_entity_lookup.

Does the AITWIRE MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the AITWIRE MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the AITWIRE MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 12, 2026.