Attify MCP server
app.attify/attifyattify.appstreamable-httpv0.3.1Scanned
Read-only Attify tools: AI agent verdicts, standards, attestations and definitions.
22 tools: 3 change things and 19 only read.
- Reads private data · 4
- Reads text others write · 2
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
3 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.
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 Attify MCP server can do
The Attify MCP server is published by attify.app, a domain the MCP Registry verified. It has 22 tools. It can create or change data (3 tools: ask_attify, define_term and verify_attestation), but cannot delete data. 19 tools only read.
4 tools read private data (compare_subjects, lookup_vendor, get_badge_embed and 1 more); 2 tools bring in text other people can write (get_badge_embed and list_traction_reports).
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 19, 2026, version 0.3.1.
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.
22 tools
Changes things 3Claude Code: ask
ask_attifyA plain-language question about the public sample audit or a published vendor's score, answered from that data only: numbers copied with their intervals and tier, every claim cited…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 A plain-language question about the public sample audit or a published vendor's score, answered from that data only: numbers copied with their intervals and tier, every claim cited (verdict fields, finding ids, evidence ids), "not in the data" instead of a guess. Requests for advice on raising a score, and for private data (brand names, source ids), are refused.
Annotations the server declares
- title: Ask Attify
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
define_termWhat a term of AI agent verification means (resolution rate, handoff, containment, meetings booked, show rate, evidence tier, provenance...): Attify's glossary definition, with how…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 What a term of AI agent verification means (resolution rate, handoff, containment, meetings booked, show rate, evidence tier, provenance...): Attify's glossary definition, with how vendors' own definitions differ where they do, and each standard's own definition in its own words, with the anchor to cite. Nothing else is guessed: an unknown term says so.
Annotations the server declares
- title: Define a term
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
verify_attestationChecks an attestation's Ed25519 signature against Attify's published keys, then whether it is still current: a vendor verification (not superseded, expired or revoked) or a tractio…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 Checks an attestation's Ed25519 signature against Attify's published keys, then whether it is still current: a vendor verification (not superseded, expired or revoked) or a traction report (not expired or withdrawn). Give the attestation JSON as published, or a vendor attestation's id.
Annotations the server declares
- title: Verify an Attify attestation
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 19Show 19 read-only tools
compare_my_agentsYour company's AI agents of one job type side by side for a month: each one's audited share of claims with its 95% interval, cost per audited outcome and main failure mode, and the…No findings
Why it is in this group
- The name "compare_my_agents" says "compare": a word for reading.
Description, as the server wrote it Your company's AI agents of one job type side by side for a month: each one's audited share of claims with its 95% interval, cost per audited outcome and main failure mode, and the pooled rate of other contributing companies where it can be shown (anonymous, each company a cluster). Differences inside the intervals are not distinguishable. Side by side comes with the Business plan. Needs sign-in to Attify; reads only.
Annotations the server declares
- title: Compare my AI agents
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
compare_subjectsTwo to five published vendors of one job type side by side: audited against claimed with 95% intervals, the gap, evidence tier, provenance, period and, for support resolution, alwa…Reads private dataNo findings
Why it is in this group
- The name "compare_subjects" says "compare": a word for reading.
What it can reach
- private-dataThe description's first sentence says "contact": it reads contacts.
Description, as the server wrote it Two to five published vendors of one job type side by side: audited against claimed with 95% intervals, the gap, evidence tier, provenance, period and, for support resolution, always each one's contact-reason mix. Vendors of different job types or standard versions are refused, and differences inside the intervals are not distinguishable.
Annotations the server declares
- title: Compare vendors
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
explain_checkWhat one check of a job type's standard asks, which question it answers (did it happen, did it stick, did a human have to redo it) and which evidence tier decides it.No findings
Why it is in this group
- The name "explain_check" says "explain": a word for reading.
Description, as the server wrote it What one check of a job type's standard asks, which question it answers (did it happen, did it stick, did a human have to redo it) and which evidence tier decides it. Checks by job type: support-resolution: "repeat_contact", "handoff", "judge_unresolved"; sales-meetings: "not_ai", "not_new", "stepped_in", "cancelled", "no_show", "not_sales"; bookings: "not_ai", "not_new", "staff_fixed", "cancelled", "no_show", "wrong_booking".
Annotations the server declares
- title: Explain a check
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
explain_provenanceWhat each provenance level means and what it can support: connected (Attify pulled every record from the customer's own system), witnessed (the vendor's agent streamed each interac…No findings
Why it is in this group
- The name "explain_provenance" says "explain": a word for reading.
Description, as the server wrote it What each provenance level means and what it can support: connected (Attify pulled every record from the customer's own system), witnessed (the vendor's agent streamed each interaction to Attify as it happened, signed and timestamped; it counts toward a verification only once the customer consented and reconciled it each month) and uploaded (a file, self-reported, never a verification). Also how an agent on its own platform sends witnessed data: the Ingest API, the Python and TypeScript SDKs, or OpenTelemetry, with the endpoints, schema and docs. Give a level to explain one.
Annotations the server declares
- title: Explain where data came from
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_agent_outcomesOne month of your company's AI agents, answer first: for each agent the verdict sentence, claimed against audited outcomes with the 95% interval, what the month cost, the cost per …No findings
Why it is in this group
- The name "get_agent_outcomes" says "get": a word for reading.
Description, as the server wrote it One month of your company's AI agents, answer first: for each agent the verdict sentence, claimed against audited outcomes with the 95% interval, what the month cost, the cost per audited outcome against the price per claimed one, and where it fails: each failure mode's share of the claims, with suggestions for your own deployment and redacted examples, quoted as customer text. For companies that buy AI agents; what a plan does not include says so. Needs sign-in to Attify; reads only.
Annotations the server declares
- title: Where my AI agents fail
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_badge_embedThe code for your live Attify badge, once a program's score is public: one line for a website (a plain link to your profile, then the script that draws the current badge and its ho…Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_badge_embed" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "email": it reads mail.
- untrusted-inputThe description's first sentence says "website": it reads web pages, which anyone can write.
Description, as the server wrote it The code for your live Attify badge, once a program's score is public: one line for a website (a plain link to your profile, then the script that draws the current badge and its hover card), the image for email signatures and READMEs, and the badge's addresses. Before that, what publishing still needs Needs sign-in to Attify; reads only.
Annotations the server declares
- title: Badge embed code
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_evidenceOne evidence record of the public sample by its id (ev_…): the outcome, the failed check, the evidence tier, the redacted excerpt, quoted as customer text, and why it failed.No findings
Why it is in this group
- The name "get_evidence" says "get": a word for reading.
Description, as the server wrote it One evidence record of the public sample by its id (ev_…): the outcome, the failed check, the evidence tier, the redacted excerpt, quoted as customer text, and why it failed.
Annotations the server declares
- title: Get an evidence record
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_indexWhat AI agents achieve, by job type: the pooled audited share of the outcomes they claimed, with its 95% interval (each company a cluster), evidence tier, provenance mix, failure m…No findings
Why it is in this group
- The name "get_index" says "get": a word for reading.
Description, as the server wrote it What AI agents achieve, by job type: the pooled audited share of the outcomes they claimed, with its 95% interval (each company a cluster), evidence tier, provenance mix, failure modes and monthly trend, from companies that contribute their anonymous data. Published for a job type only with enough contributing companies and none above half the claims. Names no company, vendor or agent. Give job_type for one job.
Annotations the server declares
- title: The Attify Index
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_ingest_healthHealth of your deployments that send witnessed data (the Ingest API, an SDK, OpenTelemetry, or read from your own agent platform account): healthy, degraded or no data and why, eve…No findings
Why it is in this group
- The name "get_ingest_health" says "get": a word for reading.
Description, as the server wrote it Health of your deployments that send witnessed data (the Ingest API, an SDK, OpenTelemetry, or read from your own agent platform account): healthy, degraded or no data and why, events and interactions in the scoring period, late interactions (never scored as witnessed), sequence gaps and breaks, the signed share, the last event, volume by month, and each customer's consent and reconciliation. Needs sign-in to Attify; reads only.
Annotations the server declares
- title: Ingest health
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_monthly_verdictYour company's verdict for a month on each AI agent it pays for, as emailed on the 1st: the verdict sentence, the audited share of the vendor's claimed outcomes with its 95% interv…No findings
Why it is in this group
- The name "get_monthly_verdict" says "get": a word for reading.
Description, as the server wrote it Your company's verdict for a month on each AI agent it pays for, as emailed on the 1st: the verdict sentence, the audited share of the vendor's claimed outcomes with its 95% interval, the cost per audited outcome, the change since the month before, the evidence tier, provenance and standard version. Last month by default. For companies that buy AI agents. Needs sign-in to Attify; reads only.
Annotations the server declares
- title: Monthly verdict
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_my_accountWho is signed in, in which organization, and what kind it is: a vendor of an AI agent, a company that buys AI agents, or an investor.No findings
Why it is in this group
- The name "get_my_account" says "get": a word for reading.
Description, as the server wrote it Who is signed in, in which organization, and what kind it is: a vendor of an AI agent, a company that buys AI agents, or an investor. Says which signed-in tools answer for it. Needs sign-in to Attify; reads only.
Annotations the server declares
- title: Your Attify account
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_program_statusYour verification programs, as a vendor: phase, public status (Claim confirmed · within 5.0 points, Claim not confirmed, Lapsed or Revoked, or private), the one next step, each pub…No findings
Why it is in this group
- The name "get_program_status" says "get": a word for reading.
Description, as the server wrote it Your verification programs, as a vendor: phase, public status (Claim confirmed · within 5.0 points, Claim not confirmed, Lapsed or Revoked, or private), the one next step, each publishing minimum met or missing in your own numbers, what the latest score still waits for before it publishes, the claimed unit as Attify recorded it, and your customers' connection and consent. It states where the program stands; it never advises how to raise a score. Needs sign-in to Attify; reads only.
Annotations the server declares
- title: Verification program status
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_renewal_packsThe renewal packs your company signed for vendor negotiations: one agent and month each, the audited numbers it carries (claimed, audited, the audited share with its interval, cost…No findings
Why it is in this group
- The name "get_renewal_packs" says "get": a word for reading.
Description, as the server wrote it The renewal packs your company signed for vendor negotiations: one agent and month each, the audited numbers it carries (claimed, audited, the audited share with its interval, cost per audited outcome), when it expires, and its signed attestation (check it with verify_attestation). Reading only: a new pack is signed in the app. Needs sign-in to Attify; reads only.
Annotations the server declares
- title: Renewal packs
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_standardA job type's published standard: number, title, version, status, how the claim is reconstructed, the checks, the evidence tiers, the changelog and the full text's address.No findings
Why it is in this group
- The name "get_standard" says "get": a word for reading.
Description, as the server wrote it A job type's published standard: number, title, version, status, how the claim is reconstructed, the checks, the evidence tiers, the changelog and the full text's address.
Annotations the server declares
- title: Get a published standard
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_traction_reportA company's audited traction report, from a share link it gave you: the summary and auditor-style opinion, up to three key numbers, each claim tested (supported, not supported, not…No findings
Why it is in this group
- The name "get_traction_report" says "get": a word for reading.
Description, as the server wrote it A company's audited traction report, from a share link it gave you: the summary and auditor-style opinion, up to three key numbers, each claim tested (supported, not supported, not testable), then usage, retention, pilot to production, concentration and outcome rates per customer-month, every number with its sample size, period, evidence tier and provenance (connected, or witnessed data the customer reconciled; never uploads), and the signed attestation. Opening it is logged in the company's view log. Links limited to named people need a browser sign-in.
Annotations the server declares
- title: Read a shared traction report
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_verdictThe answer first: one verdict sentence, then claimed, audited and the gap with 95% intervals, the evidence tier, provenance (connected, witnessed or uploaded; for witnessed data wh…No findings
Why it is in this group
- The name "get_verdict" says "get": a word for reading.
Description, as the server wrote it The answer first: one verdict sentence, then claimed, audited and the gap with 95% intervals, the evidence tier, provenance (connected, witnessed or uploaded; for witnessed data whether the customer reconciled it), judge validation, the drivers of the gap, the period, sample sizes and the data's scope. For a published vendor (by slug) or the public sample audit.
Annotations the server declares
- title: Get a verdict
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_findingsThe public sample audit's findings: each a template sentence over its numbers, with the evidence tier, sample size and the evidence ids it rests on.No findings
Why it is in this group
- The name "list_findings" says "list": a word for reading.
Description, as the server wrote it The public sample audit's findings: each a template sentence over its numbers, with the evidence tier, sample size and the evidence ids it rests on. Filter by kind: gap_driver, contact_reason, evidence_tier, judge_validation, provenance, window_sensitivity, no_request, handoff_outcome, claim_rule, rule_choice. A vendor's published score lists its drivers only (it quotes no conversation).
Annotations the server declares
- title: List findings
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_traction_reportsYour company's audited traction reports: status, summary, the months and customers covered; for one report, its share links (who each is for, state, expiry, email allowlist, views)…Reads private dataReads text others writeNo findings
Why it is in this group
- The name "list_traction_reports" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "email": it reads mail.
- untrusted-inputThe description's first sentence says "email": it reads inbound email, which other people can write.
Description, as the server wrote it Your company's audited traction reports: status, summary, the months and customers covered; for one report, its share links (who each is for, state, expiry, email allowlist, views) and who opened it, from the view log. A link's address is shown once when it is made and never stored, so it cannot be read back. Needs sign-in to Attify; reads only.
Annotations the server declares
- title: Traction reports and share links
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
lookup_vendorA vendor's published Attify verification: status (Claim confirmed · within 5.0 points when Attify is 95% sure the vendor's count overstates audited outcomes by at most the claim to…Reads private dataNo findings
Why it is in this group
- The name "lookup_vendor" says "lookup": a word for reading.
What it can reach
- private-dataThe description's first sentence says "contact": it reads contacts.
Description, as the server wrote it A vendor's published Attify verification: status (Claim confirmed · within 5.0 points when Attify is 95% sure the vendor's count overstates audited outcomes by at most the claim tolerance, the gap's upper 95% limit being within it; Claim not confirmed; Lapsed; or Revoked), audited rate against the vendor's own claimed rate with 95% intervals, the gap, evidence tier, provenance (connected, or witnessed with how many counted customers' data the vendor streamed and they reconciled), the contact-reason mix (support resolution), rank within its job type, period, standard version and the signed attestation. Give the profile slug, or a name to search. Rates compare only within one job type, and for support resolution next to the contact-reason mix.
Annotations the server declares
- title: Look up a vendor's verification
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- 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 outbound.
- Reads private data4
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- 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.
Looked at Nov 20, 2026, 18:18 UTC, unchanged since Nov 20, 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
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://attify.app/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://attify.app
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://attify.app/mcp: tools/list returned 22 tools to an anonymous client, including ask_attify (write), define_term (write), verify_attestation (write)
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 0.3.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http attify https://attify.app/mcpclaude mcp add --transport http attify https://attify.app/mcpRun 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.
{
"permissions": {
"allow": [
"mcp__attify__get_verdict",
"mcp__attify__list_findings",
"mcp__attify__get_evidence",
"mcp__attify__compare_subjects",
"mcp__attify__explain_check",
"mcp__attify__get_standard",
"mcp__attify__get_index",
"mcp__attify__lookup_vendor",
"mcp__attify__explain_provenance",
"mcp__attify__get_traction_report",
"mcp__attify__get_my_account",
"mcp__attify__get_monthly_verdict",
"mcp__attify__get_agent_outcomes",
"mcp__attify__compare_my_agents",
"mcp__attify__get_renewal_packs",
"mcp__attify__get_program_status",
"mcp__attify__get_badge_embed",
"mcp__attify__list_traction_reports",
"mcp__attify__get_ingest_health"
],
"ask": [
"mcp__attify__ask_attify",
"mcp__attify__define_term",
"mcp__attify__verify_attestation"
],
"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 attify. Review it before you use it.
Capability tags behind 4 rules
- mcp__attify__compare_subjects private-data
- mcp__attify__lookup_vendor private-data
- mcp__attify__get_badge_embed private-data, untrusted-input
- mcp__attify__list_traction_reports private-data, 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/app.attify/attify/verify?hash=7b4b23fb3ccb77ef2aa081e26953bb003bd31ac5cd5b4b5939c5ac3bd231753b" | jq -e '.changed == false'Pinned hash 7b4b23fb3ccb, from Nov 19, 2026, 21:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/app.attify/attify/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/app.attify/attify)Source: MCP Registry. Synced Nov 19, 2026, 21:17 UTC.
Attify MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Attify MCP server safe?
- No scan can promise that. What its definitions show: 22 tools, 3 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 Attify MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Attify 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 Attify MCP server have?
- 22 tools: 3 write, 19 read. ask_attify, define_term, verify_attestation, get_verdict, list_findings, get_evidence, compare_subjects, explain_check and 14 more.
Does the Attify MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Attify MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Attify MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.