← Back to search

Search • TrustOps • Plans • Shortlists • Rankings • Compare • ChatGPT compatible • Claude compatible • Healthcare • Digests • RSS • RSS XML • Backfill • MCP API

ai.anomalyarmor/armor-mcp

AnomalyArmor

Data observability tools for engineering teams: alerts, freshness, schema drift, lineage, quality.

JSON report • History API • Manage this server • Global feed

EXECUTIVE VERDICT

Executive verdict

Production trust decision: Block for production

Reason: unauthenticated behavior not proven + failing live status

Next action: revalidate, add safeguards, export policy

Status

Failing

Score

60.5

Transport

streamable-http

Tools

Current trust snapshot

Snapshot ID

trustsnap_60c26e434d80dcef

Use this ID to compare server page, report, policy, MCP, homepage, ranking, and shortlist surfaces.

Snapshot generated

May 13, 2026 06:04:01 PM UTC

All page, report, policy, and MCP surfaces use this same server-detail snapshot shape.

Last validated

May 13, 2026 05:39:46 PM UTC

Age: 0.4h • freshness band: Verified in last 24h • display score: 60.55

Production trust decision

Block for production

unauthenticated behavior not proven + failing live status

Readiness class

Needs remediation

Current validation evidence shows operational or discovery gaps that should be fixed first.

SERVER OWNER FUNNEL

Own this MCP?

Claim ownership, prove control with a GitHub, DNS, or HTTP token challenge, revalidate now, publish a badge, and configure monitoring.

1. Claim

unclaimed

Start owner claim with GitHub, DNS, or HTTP challenge instructions.

2. Revalidate

POST /v1/servers/ai.anomalyarmor/armor-mcp/revalidate

Verified owners get priority queueing after proof succeeds.

3. Badge

Verified by MCP Verify - score 60.5 - last checked May 13, 2026

4. Monitor

Pick plan + alerts

Continuous Verify plan is self-serve: choose a tier, configure watches, add authenticated validation, trigger revalidation, and use the badge.

Badge embed

[![Verified by MCP Verify](https://verify.sentinelsignal.io/badge/ai.anomalyarmor/armor-mcp.svg)](https://verify.sentinelsignal.io/servers/ai.anomalyarmor/armor-mcp)

MCP TrustOps

TrustOps turns this report into operational controls: freshness SLAs, authenticated validation, semantic benchmarks, policy exports, alert subscriptions, badges, cost/compliance metadata, and runtime routing. Fresh trusted index decisions stay separate from long-tail inventory so stale scores do not masquerade as current evidence.

Freshness band

Verified in last 24h

Policy SLA: 168.0h • confidence-weighted score: 43.9 • stale score suppressed: ✕

Policy exports

Export policy

Formats: json, rego, yaml, github_action, gateway_config, client_report

Runtime routing

/v1/route

Returns allowed tools, blocked tools, approval requirement, and reason.

Authenticated validation

Premium publisher feature: paid authenticated runs verify scopes, write-action safeguards, and authorized tool execution.

Active trust badges

Freshly Validated OAuth Verified Write-Safe No Critical Risk

Semantic benchmarks

available

Templates cover GitHub, database, healthcare, web search, and CRM least-privilege jobs.

Supply chain

metadata signal

Deep scan checks are marked separately from public metadata signals.

Compliance metadata

Terms, privacy, SOC 2, HIPAA, GDPR, retention, deletion, and audit-log fields are tracked as enterprise metadata.

Alert subscription types

Status changes Score drops or recovers Freshness SLA breach Validation schema drift OAuth or auth behavior changes Tool surface changes New or changed write tool Supply-chain signal changes Legal or compliance metadata changes

Production readiness class

Needs remediation

Current validation evidence shows operational or discovery gaps that should be fixed first.

Critical alerts

Production verdicts degrade quickly when critical alerts are active.

Evidence confidence

Confidence score

72.5

Based on 6 recent validations, 26 captured checks, and validation age of 0.4 hours.

Live checks captured

More direct checks increase trust in the current verdict.

Validation age

0.4h

Lower age means fresher evidence.

Recommended for

Generic Streamable HTTP

Generic Streamable HTTP is marked compatible with score 83.

Client compatibility verdicts

Client compatibility only means the server shape can work with a client. Production trust decision and write-action publishing are evaluated separately so a client-compatible server can still be blocked for production.

Client compatibility: ChatGPT

Partially client-compatible

tools/list must succeed.; Transport compliance should be in good shape.

Confidence: medium (72.5)

Evidence provenance

Winner: live_validation

Supporting sources: live_validation, history, server_card

Disagreements: none

initialize • Auth Required
tools_list • Error
transport_compliance_probe • Error
step_up_auth_probe • Warning
connector_replay_probe • Missing — Frozen tool snapshots must survive refresh.
request_association_probe • Missing — Roots, sampling, and elicitation should stay request-scoped.

Client compatibility: Claude

Not client-compatible

tools/list must succeed.; Transport behavior should match Claude-compatible HTTP expectations.; A useful Claude integration needs at least one exposed tool.

Confidence: medium (72.5)

Evidence provenance

Winner: live_validation

Supporting sources: live_validation, history, server_card

Disagreements: none

initialize • Auth Required
tools_list • Error
transport_compliance_probe • Error

Write-action publishing

Publishing allowed

Current write surface is bounded enough for cautious review with production policy controls.

Confidence: medium (72.5)

Evidence provenance

Winner: live_validation

Supporting sources: live_validation, history

Disagreements: none

action_safety_probe • OK

Snapshot churn risk

Low

No material tool-surface churn detected in the latest comparison.

Confidence: medium (72.5)

Evidence provenance

Winner: history

Supporting sources: history, live_validation

Disagreements: none

tool_snapshot_probe • Missing
connector_replay_probe • Missing

Why compatibility is limited by client

ChatGPT custom connector

Partial

Remediation checklist

No explicit blockers recorded.

Claude remote MCP

Blocked

Remediation checklist

No explicit blockers recorded.

Write-safe publishing

Ready

Remediation checklist

No explicit blockers recorded.

Verdict traces

Production verdict

Needs remediation

Current validation evidence shows operational or discovery gaps that should be fixed first.

Confidence: medium (72.5)

Winning source: live_validation

Triggering alerts

server_failing • critical • Latest validation is failing

Client verdict trace table

Verdict	Status	Checks	Winning source	Conflicts
`openai_connectors`	Partially client-compatible	initialize, tools_list, transport_compliance_probe, step_up_auth_probe, connector_replay_probe, request_association_probe	live_validation	none
`claude_desktop`	Not client-compatible	initialize, tools_list, transport_compliance_probe	live_validation	none
`unsafe_for_write_actions`	Publishing allowed	action_safety_probe	live_validation	none
`snapshot_churn_risk`	Low	tool_snapshot_probe, connector_replay_probe	history	none

Publishability policy profiles

ChatGPT custom connector compatibility

Compatible with review

tools/list must succeed.; Transport compliance should be in good shape. Compatibility is not a production approval; company knowledge and Messages API gates remain separate.

Search Fetch Only: No
Write Actions Present: No
Oauth Configured: Yes
Admin Refresh Required: No
Safe For Company Knowledge: No
Safe For Messages Api Remote Mcp: No

Claude remote MCP compatibility

Compatible with review

tools/list must succeed.; Transport behavior should match Claude-compatible HTTP expectations.; A useful Claude integration needs at least one exposed tool. Compatibility is not a production approval; company knowledge and Messages API gates remain separate.

Search Fetch Only: No
Write Actions Present: No
Oauth Configured: Yes
Admin Refresh Required: No
Safe For Company Knowledge: No
Safe For Messages Api Remote Mcp: No

Compatibility fixtures

ChatGPT custom connector fixture

Degraded

tools/list must succeed.; Transport compliance should be in good shape.

remote_http_endpoint: Passes
oauth_discovery: Passes
frozen_tool_snapshot_refresh: Passes
request_association: Passes

Anthropic remote MCP fixture

Degraded

tools/list must succeed.; Transport behavior should match Claude-compatible HTTP expectations.; A useful Claude integration needs at least one exposed tool.

remote_transport: Passes
tool_discovery: Likely to fail
auth_connect: Passes
safe_write_review: Passes

Authenticated validation sessions

Public validation is free. Authenticated validation is paid and proves scoped behavior, write-action safeguards, and authenticated tool execution.

Latest profile

remote_mcp

Authenticated session used

Public score isolation

✓

Preview endpoint

/v1/verify

CI preview endpoint

/v1/ci/preview

Public server reputation

Validation success 7d

0.0

Validation success 30d

0.0

Mean time to recover

n/a

Breaking diffs 30d

Registry drift frequency 30d

Snapshot changes 30d

Incident & change feed

Timestamp	Event	Details
May 13, 2026 05:39:46 PM UTC	Latest validation: failing	Score 60.5 with status failing.
May 13, 2026 05:39:46 PM UTC	Score changed	Score delta +0.3 versus the previous run.
May 13, 2026 09:32:04 AM UTC	Score changed	Score delta +0.3 versus the previous run.
May 13, 2026 01:30:28 AM UTC	Score changed	Score delta +0.1 versus the previous run.

Capabilities

OAuth: ✓
DCR/CIMD: ✓
Prompts: ✕
Homepage: https://www.anomalyarmor.ai
Docs: none
Support: none
Icon: none
Remote endpoint: https://mcp.anomalyarmor.ai/mcp
Server card: none

Use-case taxonomy

monitoring

Security posture

Tools analyzed

High-risk tools

Destructive tools

Exec tools

Egress tools

Secret tools

Bulk-access tools

Risk distribution

none

Tool capability & risk inventory

No tool inventory available from the latest validation run.

Write-action governance

Governance status

Safe to publish

✓

Auth boundary

oauth_or_auth_required

Blast radius

Low

High-risk tools

Confirmation signals

none

Safeguard count

Status detail: No unsafe write-action governance gaps detected on the latest validation.

Tool	Risk	Flags	Safeguards
No high-risk tools were detected on the latest run.

Action-controls diff

Need at least two validation runs before diffing action controls.

Why this score?

Access & Protocol

30.5/44

Connectivity, auth, and transport expectations for common clients.

Interface Quality

17.33/56

How well the tool/resource interface communicates and behaves under automation.

Security Posture

26/36

How safely the exposed tool surface handles destructive actions, egress, execution, secrets, and risky inputs.

Reliability & Trust

16.43/24

Operational stability, consistency, and trustworthiness over time.

Discovery & Governance

22.5/28

How well the server is documented, listed, and governed in public registries.

Adoption & Market

5.92/8

Adoption clues and public evidence that the server is intended for external use.

Algorithmic score breakdown

Auth Operability

4/4

Measures whether auth discovery and protected access behave predictably for clients.

Error Contract Quality

1.8/4

Grades machine-readable error structure, status alignment, and remediation hints.

Rate-Limit Semantics

2/4

Checks whether quota/throttle responses are deterministic and automation-friendly.

Schema Completeness

0/4

Completeness of tool descriptions, parameter docs, examples, and schema shape.

Backward Compatibility

4/4

Stability score across tool schema/name drift relative to prior validations.

SLO Health

3/4

Availability, latency, and burst-failure profile across recent validation history.

Security Hygiene

3/4

HTTPS posture, endpoint hygiene, and response-surface hardening checks.

Task Success

3.3/4

Can an agent reliably initialize, enumerate tools, and execute core MCP flows?

Trust Confidence

0.6/4

Confidence-adjusted reliability score that penalizes low evidence volume.

Abuse/Noise Resilience

2.5/4

How well the server preserves core behavior in the presence of noisy traffic patterns.

Prompt Contract

2/4

Quality of prompt metadata, argument shape, and prompt discoverability for clients.

Resource Contract

2/4

How completely resources and resource templates describe URIs, types, and usage shape.

Discovery Metadata

4/4

Homepage, docs, icon, repository, support, and license coverage for directory consumers.

Registry Consistency

3/4

Agreement between stored registry metadata, live server-card data, and current validation output.

Installability

2/4

How cleanly a real client can connect, initialize, enumerate tools, and proceed through auth.

Session Semantics

3.5/4

Determinism and state behavior across repeated MCP calls, including sticky-session surprises.

Tool Surface Design

0/4

Naming clarity, schema ergonomics, and parameter complexity across the tool surface.

Result Shape Stability

0/4

Stability of declared output schemas across validations, with penalties for drift or missing shapes.

OAuth Interop

4/4

Depth and client compatibility of OAuth/OIDC metadata beyond the minimal protected-resource check.

Recovery Semantics

1.5/4

Whether failures include actionable machine-readable next steps such as retry or upgrade guidance.

Maintenance Signal

2/4

Versioning, update recency, and historical validation cadence that indicate active stewardship.

Adoption Signal

2/4

Directory presence and distribution clues that suggest the server is intended for external use.

Freshness Confidence

3/4

Confidence that recent validations are current enough and dense enough to trust operationally.

Transport Fidelity

3/4

Whether declared transport metadata matches the observed endpoint behavior and response formats.

Spec Recency

2/4

How close the server’s claimed MCP protocol version is to the latest known public revision.

Session Resume

3/4

Whether Streamable HTTP session identifiers and resumed requests behave cleanly for real clients.

Step-Up Auth

3/4

Whether OAuth metadata and WWW-Authenticate challenges support granular, incremental consent instead of broad upfront scopes.

Transport Compliance

0/4

Checks session headers, protocol-version enforcement, session teardown, and expired-session behavior.

Utility Coverage

2/4

Signals support for completions, pagination, and task-oriented utility surfaces that larger clients increasingly expect.

Advanced Capability Coverage

3/4

Coverage of newer MCP surfaces like roots, sampling, elicitation, structured output, and related metadata.

Connector Publishability

3.9/4

How ready the server looks for client catalogs and managed connector programs.

Tool Snapshot Churn

0/4

Stability of the tool surface across recent validations, including add/remove and output-shape drift.

Connector Replay

3/4

Whether a previously published frozen connector snapshot would remain backward compatible after the latest tool refresh.

Request Association

3/4

Whether roots, sampling, and elicitation appear tied to active client requests instead of arriving unsolicited on idle sessions.

Interactive Flow Safety

4/4

Whether prompts and docs steer users toward safe auth flows instead of pasting secrets directly.

Action Safety

3/4

Risk-weighted view of destructive, exec, egress, and confirmation semantics across the tool surface.

Official Registry Presence

4/4

Whether the server appears directly or indirectly in the official MCP registry.

Provenance Divergence

4/4

How closely official registry metadata, the live server card, and public repo/package signals agree with each other.

Safety Transparency

3/4

Clarity of docs, auth disclosure, support links, and other trust signals visible to integrators.

Tool Capability Clarity

0/4

How clearly the tool surface communicates whether each action reads, writes, deletes, executes, or exports data.

Destructive Operation Safety

3/4

Penalizes delete/revoke/destroy style tools unless auth and safeguards reduce blast radius.

Egress / SSRF Resilience

3/4

Assesses arbitrary URL fetch, crawl, webhook, and remote-request exposure on the tool surface.

Execution / Sandbox Safety

4/4

Evaluates shell, code, script, and command-execution exposure and whether that surface appears contained.

Data Exfiltration Resilience

3/4

Assesses export, dump, backup, and bulk-read behavior against the surrounding auth and safeguard signals.

Least Privilege Scope

3/4

Rewards scoped auth metadata and penalizes broad or missing scopes around privileged tools.

Secret Handling Hygiene

3/4

Assesses secret-bearing tools, token leakage risk, and whether the public surface avoids obvious secret exposure.

Supply Chain Signal

2.5/4

Public metadata signal for repository, changelog, license, versioning, and recency that supports supply-chain trust.

Input Sanitization Safety

0/4

Penalizes risky freeform string inputs when schemas do not constrain URLs, code, paths, queries, or templates.

Tool Namespace Clarity

0/4

Measures naming uniqueness and ambiguity across the tool namespace to reduce collision and confusion risk.

Compatibility profiles

OpenAI Connectors

77.8

partial

tools/list must succeed.; Transport compliance should be in good shape.

Connector URL: https://mcp.anomalyarmor.ai/mcp
# Complete OAuth in the client when prompted.
# Server: ai.anomalyarmor/armor-mcp

Claude Desktop

50.0

blocked

tools/list must succeed.; Transport behavior should match Claude-compatible HTTP expectations.; A useful Claude integration needs at least one exposed tool.

{
  "mcpServers": {
    "armor-mcp": {
      "command": "npx",
      "args": ["mcp-remote", "https://mcp.anomalyarmor.ai/mcp"]
    }
  }
}

Smithery

60.0

partial

Tool discovery must succeed.; Machine-readable failure semantics should be present.

smithery mcp add "https://mcp.anomalyarmor.ai/mcp"

Generic Streamable HTTP

83.3

compatible

tools/list must succeed.

curl -sS https://mcp.anomalyarmor.ai/mcp -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"mcp-verify","version":"0.1.0"}}}'

Actionable remediation

Severity	Remediation	Why it matters	Recommended action
Critical	Ensure tools/list succeeds consistently	Tools discovery is the minimum viable contract for most MCP clients and directories.	Make tools/list succeed unauthenticated when possible, or document the auth flow in the server card. Playbook Make `tools/list` deterministic across repeated calls. Document or relax auth requirements for discovery routes. Check that tool names, descriptions, and schemas remain stable across deploys.
Critical	Make initialize deterministic and client-friendly	If initialize fails or requires undocumented auth, many MCP clients cannot connect.	Allow initialize to succeed consistently, or return a deterministic auth-required response with clear metadata. Playbook Allow `initialize` to succeed unauthenticated when possible. If auth is required, return a deterministic auth-required response and matching metadata. Retest against `https://mcp.anomalyarmor.ai/mcp` from a clean client session.
Critical	Respond to latest validation is failing	Core MCP flows did not validate successfully on the latest run.	Fix the failing checks first, then revalidate to confirm the recovery path. Playbook Fix the failing checks first. Review the latest incident feed and validation diff for the first regression. Revalidate once the remediation lands.
High	Align session and protocol behavior with Streamable HTTP expectations	Clients increasingly rely on MCP-Protocol-Version, session teardown, and expired-session semantics.	Align MCP-Protocol-Version, MCP-Session-Id, DELETE teardown, and expired-session handling with the transport spec. Playbook Return `Mcp-Session-Id` and `Mcp-Protocol-Version` headers consistently on streamable HTTP responses. Honor `DELETE` session teardown and return `404` when a deleted session is reused. Reject invalid protocol-version headers with `400 Bad Request`.
High	Associate roots, sampling, and elicitation with active client requests	Modern MCP guidance expects roots, sampling, and elicitation traffic to be tied to an active client request instead of arriving unsolicited on idle sessions.	Inspect the latest validation evidence and resolve the client-visible regression. Playbook Inspect the latest validation evidence. Resolve the highest-severity client-facing gap first. Revalidate and confirm the score and verdict improve.
High	Keep connector refreshes backward compatible	Managed connector clients freeze tool snapshots, so removed tools, new required args, and breaking output changes can break published integrations after refresh.	Inspect the latest validation evidence and resolve the client-visible regression. Playbook Inspect the latest validation evidence. Resolve the highest-severity client-facing gap first. Revalidate and confirm the score and verdict improve.
Medium	Adopt a current MCP protocol revision	Older protocol revisions reduce compatibility with newer clients and registry programs.	Inspect the latest validation evidence and resolve the client-visible regression. Playbook Inspect the latest validation evidence. Resolve the highest-severity client-facing gap first. Revalidate and confirm the score and verdict improve.
Medium	Close connector-publishing gaps	Connector catalogs care about protocol recency, session behavior, auth clarity, and tool-surface stability.	Inspect the latest validation evidence and resolve the client-visible regression. Playbook Inspect the latest validation evidence. Resolve the highest-severity client-facing gap first. Revalidate and confirm the score and verdict improve.
Medium	Document minimal scopes and return cleaner auth challenges	Modern clients expect granular scopes and step-up auth signals such as WWW-Authenticate scope hints.	Return granular scopes and WWW-Authenticate challenge hints instead of forcing overly broad auth upfront. Playbook Advertise the narrowest viable scopes in OAuth metadata. Return `WWW-Authenticate` challenges with scope or insufficient-scope hints when additional consent is needed. Revalidate with both public discovery and auth-required flows.
Medium	Raise Interface Quality score	How well the tool/resource interface communicates and behaves under automation.	Improve schemas, error contracts, and recovery messages so agents can reason about the surface automatically. Playbook Inspect the latest validation evidence. Resolve the highest-severity client-facing gap first. Revalidate and confirm the score and verdict improve.
Medium	Reduce tool-surface churn	Frequent add/remove or output-shape drift makes published connectors and cached tool snapshots brittle.	Inspect the latest validation evidence and resolve the client-visible regression. Playbook Inspect the latest validation evidence. Resolve the highest-severity client-facing gap first. Revalidate and confirm the score and verdict improve.
Medium	Repair prompts/list or stop advertising prompts	Prompt metadata should either work live or be removed from the advertised capability set.	Only advertise prompts if prompts/list works and prompt arguments are documented. Playbook Only advertise prompts that are actually accessible. Add prompt descriptions and argument docs. Run a live `prompts/list` check after any prompt changes.
Medium	Repair resources/list or stop advertising resources	Resource metadata should either work live or be removed from the advertised capability set.	Only advertise resources if resources/list works and resources expose stable URIs/types. Playbook Only advertise resources with stable URIs and read semantics. Add MIME/type hints where possible. Run a live `resources/list` and `resources/read` check after updates.
Medium	Support resumable HTTP sessions cleanly	Modern MCP clients increasingly expect resumable session behavior on streamable HTTP transports.	Inspect the latest validation evidence and resolve the client-visible regression. Playbook Inspect the latest validation evidence. Resolve the highest-severity client-facing gap first. Revalidate and confirm the score and verdict improve.
Low	Publish newer MCP capability signals	Roots, sampling, elicitation, structured outputs, and related metadata improve client understanding and ranking.	Inspect the latest validation evidence and resolve the client-visible regression. Playbook Inspect the latest validation evidence. Resolve the highest-severity client-facing gap first. Revalidate and confirm the score and verdict improve.

Point loss breakdown

Component	Current	Points missing
Transport Compliance	0/4	-4.0
Tool Surface Design	0/4	-4.0
Tool Snapshot Churn	0/4	-4.0
Tool Namespace Clarity	0/4	-4.0
Tool Capability Clarity	0/4	-4.0
Schema Completeness	0/4	-4.0
Result Shape Stability	0/4	-4.0
Input Sanitization Safety	0/4	-4.0
Trust Confidence	0.6/4	-3.4
Recovery Semantics	1.5/4	-2.5
Error Contract	1.8/4	-2.2
Utility Coverage	2/4	-2.0

Validation diff

Score delta

0.31

Summary changed

Tool delta

Prompt delta

Auth mode changed

Write surface expanded

Protocol regressed

Registry drift changed

Regressed checks: none

Improved checks: none

Component	Previous	Latest	Delta
`freshness_confidence_score`	2.5	3.0	0.5
`trust_confidence_score`	0.5	0.6	0.1

Tool snapshot diff & changelog

Need at least two validation runs before building a tool changelog.

Connector replay

Status

Missing

Backward compatible

Would break after refresh

Added tools

none

Removed tools

none

Additive output changes

none

Required-argument replay breaks

Tool	Added required args	Removed required args
No required-argument replay breaks detected.

Output-schema replay breaks

Tool	Removed properties	Added properties
No output-schema replay breaks detected.

Transport compliance drilldown

Probe status

Error

Transport

streamable-http

Session header

Protocol header

Bad protocol response

401

DELETE teardown

n/a

Expired session retry

n/a

Last-Event-ID visible

Issues: missing_protocol_header, bad_protocol_not_rejected

Request association

Status

Missing

Advertised capabilities

none

Observed idle methods

none

Violating methods

none

Probe HTTP status

n/a

Issues

none

Utility coverage

Probe status

Completions

not detected

Completion probe target: none

Pagination

supported

No nextCursor evidence.

Tasks

Auth Required

Advertised: no

Benchmark tasks

Benchmark task	Status	Evidence
Discover tools	Likely to fail	`initialize` • Auth Required `tools_list` • Error
Read-only fetch flow	Likely to fail	`resource_read` • Missing `read_only_tool_surface` • Missing
OAuth-required connect	Passes	`oauth_protected_resource` • OK `step_up_auth_probe` • Warning
Safe write flow with confirmation	Passes	`action_safety_probe` • OK

Registry & provenance divergence

Probe status

Direct official match

yes

Drift fields

none

Field	Registry	Live server card
Title	n/a	AnomalyArmor
Version	n/a	0.7.0
Homepage	n/a	n/a

Active alerts

Latest validation is failing (critical)
Core MCP flows did not validate successfully on the latest run.

Aliases & registry graph

Identifier	Source	Canonical	Score
`ai.anomalyarmor/armor-mcp`	official_registry	yes	60.55

Alias consolidation

Canonical identifier

ai.anomalyarmor/armor-mcp

Duplicate aliases

Registry sources

official_registry

Remote URLs

https://mcp.anomalyarmor.ai/mcp

Homepages

https://www.anomalyarmor.ai

Source disagreements

Field	What differs	Observed values
No source disagreements detected.

Install snippets

Openai Connectors

Connector URL: https://mcp.anomalyarmor.ai/mcp
# Complete OAuth in the client when prompted.
# Server: ai.anomalyarmor/armor-mcp

Claude Desktop

{
  "mcpServers": {
    "armor-mcp": {
      "command": "npx",
      "args": ["mcp-remote", "https://mcp.anomalyarmor.ai/mcp"]
    }
  }
}

Smithery

smithery mcp add "https://mcp.anomalyarmor.ai/mcp"

Generic Http

curl -sS https://mcp.anomalyarmor.ai/mcp -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"mcp-verify","version":"0.1.0"}}}'

Agent access & tool surface

Live server tools

No live tool surface captured yet.

Observed from the latest live validation against https://mcp.anomalyarmor.ai/mcp. This is the target server surface, not Verify's own inspection tools.

Live capability counts

0 tools • 0 prompts • 0 resources

Counts come from the latest tools/list, prompts/list, and resources/list checks.

Inspect with Verify

search fetch search_servers recommend_servers get_server_report compare_servers

Use Verify itself to search, recommend, compare, and fetch the full report for ai.anomalyarmor/armor-mcp.

Direct machine links

JSON report • Compare this server • Verify MCP API

Claims & monitoring

Server ownership

No verified maintainer claim recorded.

Watch subscriptions

Teams: none

Alert routing

Active watches

Generic webhooks

Slack routes

Teams routes

Email routes

Watch	Team	Channels	Minimum severity
No active watch destinations.

Maintainer analytics

Validation Run Count

Average Latency Ms

751.63

Healthy Run Ratio Recent

0.0

Registry Presence Count

Active Alert Count

Watcher Count

Verified Claim

False

Taxonomy Tags

monitoring

Score Trend

60.55, 60.24, 59.94, 59.82, 59.71, 55.96

Remediation Count

High Risk Tool Count

Destructive Tool Count

Exec Tool Count

Maintainer response quality

Score

16.67

Verified claim

Support contact

Changelog present

Incident notes present

Tool changes documented

✓

Annotation history

Annotation count

Maintainer annotations

No maintainer annotations have been recorded yet.

Maintainer rebuttals & expected behavior

No maintainer rebuttals or expected-behavior overrides are recorded yet.

Latest validation evidence

Latest summary

Failing

Validation profile

remote_mcp

Started

May 13, 2026 05:39:45 PM UTC

Latency

986.0 ms

Failures

initialize Client error '401 Unauthorized' for url 'https://mcp.anomalyarmor.ai/mcp' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/401
prompts_list Client error '401 Unauthorized' for url 'https://mcp.anomalyarmor.ai/mcp' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/401
resources_list Client error '401 Unauthorized' for url 'https://mcp.anomalyarmor.ai/mcp' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/401
tools_list Client error '401 Unauthorized' for url 'https://mcp.anomalyarmor.ai/mcp' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/401
transport_compliance_probe Issues: missing protocol header, bad protocol not rejected (bad protocol=401).

Checks

Check	Status	Latency	Evidence
`action_safety_probe`	OK	n/a	No high-risk write, destructive, or exec tools detected.
`advanced_capabilities_probe`	Warning	n/a	Only 2 capability signal(s): prompts, resources.
`connector_publishability_probe`	Error	n/a	Publishability blockers: tools list, protocol version, transport compliance, tool surface.
`connector_replay_probe`	Missing	n/a	No connector replay evidence recorded.
`determinism_probe`	Missing	n/a	tools list unavailable
`initialize`	Auth Required	10.1 ms	Client error '401 Unauthorized' for url 'https://mcp.anomalyarmor.ai/mcp' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/401
`interactive_flow_probe`	OK	n/a	Check completed
`oauth_authorization_server`	OK	333.9 ms	authorization_endpoint, claims_supported, code_challenge_methods_supported, grant_types_supported
`oauth_protected_resource`	OK	12.7 ms	1 authorization server(s)
`official_registry_probe`	OK	n/a	Check completed
`openid_configuration`	OK	124.8 ms	authorization_endpoint, backchannel_logout_supported, claims_supported, code_challenge_methods_supported
`probe_noise_resilience`	OK	46.0 ms	Fetched https://mcp.anomalyarmor.ai/robots.txt
`prompt_get`	Missing	n/a	no prompt name
`prompts_list`	Auth Required	58.4 ms	Client error '401 Unauthorized' for url 'https://mcp.anomalyarmor.ai/mcp' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/401
`protocol_version_probe`	Missing	n/a	No protocol version was advertised.
`provenance_divergence_probe`	OK	n/a	Check completed
`request_association_probe`	Missing	n/a	No request-association capabilities were advertised.
`resource_read`	Missing	n/a	no resource uri
`resources_list`	Auth Required	48.1 ms	Client error '401 Unauthorized' for url 'https://mcp.anomalyarmor.ai/mcp' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/401
`server_card`	OK	231.8 ms	$schema, authentication, capabilities, description
`session_resume_probe`	Missing	n/a	no session id
`step_up_auth_probe`	Warning	n/a	Scopes=email, offline access, openid, private metadata, +2 more; step-up challenge hints present.
`tool_snapshot_probe`	Missing	n/a	no tools
`tools_list`	Error	61.0 ms	Client error '401 Unauthorized' for url 'https://mcp.anomalyarmor.ai/mcp' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/401
`transport_compliance_probe`	Error	37.7 ms	Issues: missing protocol header, bad protocol not rejected (bad protocol=401).
`utility_coverage_probe`	OK	11.6 ms	No completions evidence; pagination supported; tasks auth required.

Raw evidence view

Show raw JSON evidence

{
  "checks": {
    "action_safety_probe": {
      "details": {
        "auth_present": true,
        "confirmation_signals": [],
        "safeguard_count": 0,
        "summary": {
          "bulk_access_tools": 0,
          "capability_distribution": {},
          "destructive_tools": 0,
          "egress_tools": 0,
          "exec_tools": 0,
          "high_risk_tools": 0,
          "risk_distribution": {
            "critical": 0,
            "high": 0,
            "low": 0,
            "medium": 0
          },
          "secret_tools": 0,
          "tool_count": 0
        }
      },
      "latency_ms": null,
      "status": "ok"
    },
    "advanced_capabilities_probe": {
      "details": {
        "capabilities": {
          "completions": false,
          "elicitation": false,
          "prompts": true,
          "resource_links": false,
          "resources": true,
          "roots": false,
          "sampling": false,
          "structured_outputs": false
        },
        "enabled": [
          "prompts",
          "resources"
        ],
        "enabled_count": 2,
        "initialize_capability_keys": []
      },
      "latency_ms": null,
      "status": "warning"
    },
    "connector_publishability_probe": {
      "details": {
        "blockers": [
          "tools_list",
          "protocol_version",
          "transport_compliance",
          "tool_surface"
        ],
        "criteria": {
          "action_safety": true,
          "auth_flow": true,
          "connector_replay": true,
          "initialize": true,
          "protocol_version": false,
          "remote_transport": true,
          "request_association": true,
          "server_card": true,
          "session_resume": true,
          "step_up_auth": true,
          "tool_surface": false,
          "tools_list": false,
          "transport_compliance": false
        },
        "high_risk_tools": 0,
        "tool_count": 0,
        "transport": "streamable-http"
      },
      "latency_ms": null,
      "status": "error"
    },
    "connector_replay_probe": {
      "details": {
        "reason": "no_tools"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "determinism_probe": {
      "details": {
        "reason": "tools_list_unavailable"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "initialize": {
      "details": {
        "error": "Client error '401 Unauthorized' for url 'https://mcp.anomalyarmor.ai/mcp'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/401",
        "headers": {
          "content-type": "application/json",
          "www-authenticate": "Bearer error=\"invalid_token\", error_description=\"Authentication failed. The provided bearer token is invalid, expired, or no longer recognized by the server. To resolve: clear authentication tokens in your MCP client and reconnect. Your client should automatically re-register and obtain new tokens.\", resource_metadata=\"https://mcp.anomalyarmor.ai/.well-known/oauth-protected-resource/mcp\""
        },
        "http_status": 401,
        "payload": {},
        "url": "https://mcp.anomalyarmor.ai/mcp"
      },
      "latency_ms": 10.11,
      "status": "auth_required"
    },
    "interactive_flow_probe": {
      "details": {
        "oauth_supported": true,
        "prompt_available": false,
        "risk_hits": [],
        "safe_hits": [
          "oauth"
        ]
      },
      "latency_ms": null,
      "status": "ok"
    },
    "oauth_authorization_server": {
      "details": {
        "headers": {
          "content-type": "application/json",
          "set-cookie": "__cf_bm=DhBT0NYg9WKyF9k7vKLNfGNIeN7oMkEhyY4U5GFFbb8-1778693986-1.0.1.1-3eTQJEAyVgVFeBFLR6Hk2Yx4Z8SG01DIhQirroSn4BBhDRZMjNntgVnHF_08H9Qm4T2zOEXLNIrVjW8ytKPYyIwrzexC6WJEH.jNt09n_kg; path=/; expires=Wed, 13-May-26 18:09:46 GMT; domain=.clerk.anomalyarmor.ai; HttpOnly; Secure; SameSite=None, _cfuvid=Cnl28voH3UhQ20ypfVnSO7RQ41V4agLYrzqk72Yhf7k-1778693986294-0.0.1.1-604800000; path=/; domain=.clerk.anomalyarmor.ai; HttpOnly; Secure; SameSite=None",
          "strict-transport-security": "max-age=63072000;"
        },
        "http_status": 200,
        "payload": {
          "authorization_endpoint": "https://clerk.anomalyarmor.ai/oauth/authorize",
          "claims_supported": [
            "sub",
            "iss",
            "aud",
            "exp",
            "iat",
            "email",
            "name"
          ],
          "code_challenge_methods_supported": [
            "S256"
          ],
          "grant_types_supported": [
            "authorization_code",
            "refresh_token"
          ],
          "id_token_signing_alg_values_supported": [
            "RS256"
          ],
          "issuer": "https://clerk.anomalyarmor.ai",
          "jwks_uri": "https://clerk.anomalyarmor.ai/.well-known/jwks.json",
          "op_tos_uri": "https://clerk.com/legal/standard-terms",
          "registration_endpoint": "https://clerk.anomalyarmor.ai/oauth/register",
          "response_types_supported": [
            "code"
          ],
          "revocation_endpoint": "https://clerk.anomalyarmor.ai/oauth/token/revoke",
          "scopes_supported": [
            "openid",
            "profile",
            "email",
            "public_metadata",
            "private_metadata",
            "offline_access"
          ],
          "service_documentation": "https://clerk.com/docs/oauth/scoped-access",
          "subject_types_supported": [
            "public"
          ],
          "token_endpoint": "https://clerk.anomalyarmor.ai/oauth/token",
          "token_endpoint_auth_methods_supported": [
            "client_secret_basic",
            "none",
            "client_secret_post"
          ],
          "ui_locales_supported": [
            "en"
          ]
        },
        "url": "https://clerk.anomalyarmor.ai/.well-known/oauth-authorization-server"
      },
      "latency_ms": 333.89,
      "status": "ok"
    },
    "oauth_protected_resource": {
      "details": {
        "headers": {
          "content-type": "application/json"
        },
        "http_status": 200,
        "payload": {
          "authorization_servers": [
            "https://clerk.anomalyarmor.ai/"
          ],
          "bearer_methods_supported": [
            "header"
          ],
          "resource": "https://mcp.anomalyarmor.ai/mcp",
          "resource_name": "AnomalyArmor MCP Server",
          "scopes_supported": []
        },
        "url": "https://mcp.anomalyarmor.ai/.well-known/oauth-protected-resource"
      },
      "latency_ms": 12.68,
      "status": "ok"
    },
    "official_registry_probe": {
      "details": {
        "direct_match": true,
        "official_peer_count": 1,
        "registry_identifier": "ai.anomalyarmor/armor-mcp",
        "registry_source": "official_registry"
      },
      "latency_ms": null,
      "status": "ok"
    },
    "openid_configuration": {
      "details": {
        "headers": {
          "content-type": "application/json",
          "strict-transport-security": "max-age=63072000;"
        },
        "http_status": 200,
        "payload": {
          "authorization_endpoint": "https://clerk.anomalyarmor.ai/oauth/authorize",
          "backchannel_logout_supported": false,
          "claims_supported": [
            "aud",
            "iss",
            "iat",
            "email",
            "email_verified",
            "family_name",
            "name",
            "preferred_username",
            "sub",
            "exp",
            "given_name",
            "picture"
          ],
          "code_challenge_methods_supported": [
            "S256"
          ],
          "frontchannel_logout_supported": false,
          "grant_types_supported": [
            "authorization_code",
            "refresh_token"
          ],
          "id_token_signing_alg_values_supported": [
            "RS256"
          ],
          "introspection_endpoint": "https://clerk.anomalyarmor.ai/oauth/token_info",
          "issuer": "https://clerk.anomalyarmor.ai",
          "jwks_uri": "https://clerk.anomalyarmor.ai/.well-known/jwks.json",
          "response_modes_supported": [
            "form_post",
            "query"
          ],
          "response_types_supported": [
            "code"
          ],
          "revocation_endpoint": "https://clerk.anomalyarmor.ai/oauth/token/revoke",
          "scopes_supported": [
            "email",
            "profile",
            "public_metadata",
            "private_metadata",
            "openid",
            "offline_access"
          ],
          "subject_types_supported": [
            "public"
          ],
          "token_endpoint": "https://clerk.anomalyarmor.ai/oauth/token",
          "token_endpoint_auth_methods_supported": [
            "client_secret_basic",
            "none",
            "client_secret_post"
          ],
          "userinfo_endpoint": "https://clerk.anomalyarmor.ai/oauth/userinfo"
        },
        "url": "https://clerk.anomalyarmor.ai/.well-known/openid-configuration"
      },
      "latency_ms": 124.75,
      "status": "ok"
    },
    "probe_noise_resilience": {
      "details": {
        "headers": {
          "content-type": "text/plain; charset=utf-8"
        },
        "http_status": 200,
        "url": "https://mcp.anomalyarmor.ai/robots.txt"
      },
      "latency_ms": 45.95,
      "status": "ok"
    },
    "prompt_get": {
      "details": {
        "reason": "no_prompt_name"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "prompts_list": {
      "details": {
        "error": "Client error '401 Unauthorized' for url 'https://mcp.anomalyarmor.ai/mcp'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/401",
        "headers": {
          "content-type": "application/json",
          "www-authenticate": "Bearer error=\"invalid_token\", error_description=\"Authentication failed. The provided bearer token is invalid, expired, or no longer recognized by the server. To resolve: clear authentication tokens in your MCP client and reconnect. Your client should automatically re-register and obtain new tokens.\", resource_metadata=\"https://mcp.anomalyarmor.ai/.well-known/oauth-protected-resource/mcp\""
        },
        "http_status": 401,
        "payload": {},
        "reason": "auth_required",
        "url": "https://mcp.anomalyarmor.ai/mcp"
      },
      "latency_ms": 58.37,
      "status": "auth_required"
    },
    "protocol_version_probe": {
      "details": {
        "latest_known_version": "2025-11-25",
        "reason": "no_protocol_version",
        "validator_protocol_version": "2025-03-26"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "provenance_divergence_probe": {
      "details": {
        "direct_official_match": true,
        "drift_fields": [],
        "metadata_document_count": 3,
        "registry_homepage": null,
        "registry_repository": null,
        "registry_title": null,
        "registry_version": null,
        "server_card_homepage": null,
        "server_card_repository": null,
        "server_card_title": "AnomalyArmor",
        "server_card_version": "0.7.0"
      },
      "latency_ms": null,
      "status": "ok"
    },
    "request_association_probe": {
      "details": {
        "reason": "no_request_association_capabilities_advertised"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "resource_read": {
      "details": {
        "reason": "no_resource_uri"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "resources_list": {
      "details": {
        "error": "Client error '401 Unauthorized' for url 'https://mcp.anomalyarmor.ai/mcp'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/401",
        "headers": {
          "content-type": "application/json",
          "www-authenticate": "Bearer error=\"invalid_token\", error_description=\"Authentication failed. The provided bearer token is invalid, expired, or no longer recognized by the server. To resolve: clear authentication tokens in your MCP client and reconnect. Your client should automatically re-register and obtain new tokens.\", resource_metadata=\"https://mcp.anomalyarmor.ai/.well-known/oauth-protected-resource/mcp\""
        },
        "http_status": 401,
        "payload": {},
        "reason": "auth_required",
        "url": "https://mcp.anomalyarmor.ai/mcp"
      },
      "latency_ms": 48.06,
      "status": "auth_required"
    },
    "server_card": {
      "details": {
        "headers": {
          "content-type": "application/json"
        },
        "http_status": 200,
        "payload": {
          "$schema": "https://modelcontextprotocol.io/schemas/server-card/draft-1.json",
          "authentication": {
            "oauthProtectedResource": "https://mcp.anomalyarmor.ai/.well-known/oauth-protected-resource/mcp",
            "type": "oauth2"
          },
          "capabilities": {
            "prompts": {
              "listChanged": true
            },
            "resources": {
              "listChanged": true
            },
            "tools": {
              "categories": [
                "catalog",
                "destinations",
                "freshness",
                "alerts",
                "health",
                "recommendations",
                "intelligence"
              ],
              "listChanged": true
            }
          },
          "description": "Data observability tools for AI assistants. Query alerts, monitor freshness, inspect schema changes, and manage destinations via natural language.",
          "installation": {
            "claudeCode": "claude mcp add anomalyarmor --transport http https://mcp.anomalyarmor.ai/mcp",
            "cursor": {
              "mcpServers": {
                "anomalyarmor": {
                  "url": "https://mcp.anomalyarmor.ai/mcp"
                }
              }
            },
            "local": {
              "args": [
                "armor-mcp"
              ],
              "command": "uvx",
              "env": {
                "ARMOR_API_KEY": "aa_live_your_key_here"
              }
            }
          },
          "name": "AnomalyArmor",
          "serverInfo": {
            "description": "Data observability tools for AI assistants. Query alerts, monitor freshness, inspect schema changes, and manage destinations via natural language.",
            "documentation": "https://docs.anomalyarmor.ai/integrations/mcp-server",
            "homepage": "https://www.anomalyarmor.ai",
            "name": "AnomalyArmor",
            "title": "AnomalyArmor MCP Server",
            "vendor": {
              "name": "AnomalyArmor",
              "supportEmail": "support@anomalyarmor.ai",
              "url": "https://www.anomalyarmor.ai"
            },
            "version": "0.7.0"
          },
          "serverUrl": "https://mcp.anomalyarmor.ai/mcp",
          "transports": [
            {
              "preferred": true,
              "type": "streamable-http",
              "url": "https://mcp.anomalyarmor.ai/mcp"
            }
          ],
          "version": "0.7.0"
        },
        "url": "https://mcp.anomalyarmor.ai/.well-known/mcp/server-card.json"
      },
      "latency_ms": 231.75,
      "status": "ok"
    },
    "session_resume_probe": {
      "details": {
        "protocol_version": null,
        "reason": "no_session_id",
        "resume_expected": false,
        "transport": "streamable-http"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "step_up_auth_probe": {
      "details": {
        "auth_required_checks": [
          "initialize",
          "prompts_list",
          "resources_list"
        ],
        "broad_scopes": [],
        "challenge_headers": [
          "Bearer error=\"invalid_token\", error_description=\"Authentication failed. The provided bearer token is invalid, expired, or no longer recognized by the server. To resolve: clear authentication tokens in your MCP client and reconnect. Your client should automatically re-register and obtain new tokens.\", resource_metadata=\"https://mcp.anomalyarmor.ai/.well-known/oauth-protected-resource/mcp\"",
          "Bearer error=\"invalid_token\", error_description=\"Authentication failed. The provided bearer token is invalid, expired, or no longer recognized by the server. To resolve: clear authentication tokens in your MCP client and reconnect. Your client should automatically re-register and obtain new tokens.\", resource_metadata=\"https://mcp.anomalyarmor.ai/.well-known/oauth-protected-resource/mcp\"",
          "Bearer error=\"invalid_token\", error_description=\"Authentication failed. The provided bearer token is invalid, expired, or no longer recognized by the server. To resolve: clear authentication tokens in your MCP client and reconnect. Your client should automatically re-register and obtain new tokens.\", resource_metadata=\"https://mcp.anomalyarmor.ai/.well-known/oauth-protected-resource/mcp\""
        ],
        "minimal_scope_documented": false,
        "oauth_present": true,
        "scope_specificity_ratio": 0.1429,
        "step_up_signals": [
          "Bearer error=\"invalid_token\", error_description=\"Authentication failed. The provided bearer token is invalid, expired, or no longer recognized by the server. To resolve: clear authentication tokens in your MCP client and reconnect. Your client should automatically re-register and obtain new tokens.\", resource_metadata=\"https://mcp.anomalyarmor.ai/.well-known/oauth-protected-resource/mcp\"",
          "Bearer error=\"invalid_token\", error_description=\"Authentication failed. The provided bearer token is invalid, expired, or no longer recognized by the server. To resolve: clear authentication tokens in your MCP client and reconnect. Your client should automatically re-register and obtain new tokens.\", resource_metadata=\"https://mcp.anomalyarmor.ai/.well-known/oauth-protected-resource/mcp\"",
          "Bearer error=\"invalid_token\", error_description=\"Authentication failed. The provided bearer token is invalid, expired, or no longer recognized by the server. To resolve: clear authentication tokens in your MCP client and reconnect. Your client should automatically re-register and obtain new tokens.\", resource_metadata=\"https://mcp.anomalyarmor.ai/.well-known/oauth-protected-resource/mcp\""
        ],
        "supported_scopes": [
          "email",
          "offline_access",
          "openid",
          "private_metadata",
          "profile",
          "public_metadata"
        ]
      },
      "latency_ms": null,
      "status": "warning"
    },
    "tool_snapshot_probe": {
      "details": {
        "reason": "no_tools"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "tools_list": {
      "details": {
        "error": "Client error '401 Unauthorized' for url 'https://mcp.anomalyarmor.ai/mcp'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/401",
        "headers": {
          "content-type": "application/json",
          "www-authenticate": "Bearer error=\"invalid_token\", error_description=\"Authentication failed. The provided bearer token is invalid, expired, or no longer recognized by the server. To resolve: clear authentication tokens in your MCP client and reconnect. Your client should automatically re-register and obtain new tokens.\", resource_metadata=\"https://mcp.anomalyarmor.ai/.well-known/oauth-protected-resource/mcp\""
        },
        "http_status": 401,
        "payload": {},
        "url": "https://mcp.anomalyarmor.ai/mcp"
      },
      "latency_ms": 60.97,
      "status": "error"
    },
    "transport_compliance_probe": {
      "details": {
        "bad_protocol_error": null,
        "bad_protocol_headers": {
          "content-type": "application/json",
          "www-authenticate": "Bearer error=\"invalid_token\", error_description=\"Authentication failed. The provided bearer token is invalid, expired, or no longer recognized by the server. To resolve: clear authentication tokens in your MCP client and reconnect. Your client should automatically re-register and obtain new tokens.\", resource_metadata=\"https://mcp.anomalyarmor.ai/.well-known/oauth-protected-resource/mcp\""
        },
        "bad_protocol_payload": {
          "error": "invalid_token",
          "error_description": "Authentication failed. The provided bearer token is invalid, expired, or no longer recognized by the server. To resolve: clear authentication tokens in your MCP client and reconnect. Your client should automatically re-register and obtain new tokens."
        },
        "bad_protocol_status_code": 401,
        "delete_error": null,
        "delete_status_code": null,
        "expired_session_error": null,
        "expired_session_status_code": null,
        "issues": [
          "missing_protocol_header",
          "bad_protocol_not_rejected"
        ],
        "last_event_id_visible": false,
        "protocol_header_present": false,
        "requested_protocol_version": "2025-03-26",
        "session_id_present": false,
        "transport": "streamable-http"
      },
      "latency_ms": 37.74,
      "status": "error"
    },
    "utility_coverage_probe": {
      "details": {
        "completions": {
          "advertised": false,
          "live_probe": "not_executed",
          "sample_target": null
        },
        "initialize_capability_keys": [],
        "pagination": {
          "metadata_signal": true,
          "next_cursor_methods": [],
          "supported": true
        },
        "tasks": {
          "advertised": false,
          "http_status": 401,
          "probe_status": "auth_required"
        }
      },
      "latency_ms": 11.56,
      "status": "ok"
    }
  },
  "failures": {
    "initialize": {
      "error": "Client error '401 Unauthorized' for url 'https://mcp.anomalyarmor.ai/mcp'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/401",
      "headers": {
        "content-type": "application/json",
        "www-authenticate": "Bearer error=\"invalid_token\", error_description=\"Authentication failed. The provided bearer token is invalid, expired, or no longer recognized by the server. To resolve: clear authentication tokens in your MCP client and reconnect. Your client should automatically re-register and obtain new tokens.\", resource_metadata=\"https://mcp.anomalyarmor.ai/.well-known/oauth-protected-resource/mcp\""
      },
      "http_status": 401,
      "payload": {},
      "url": "https://mcp.anomalyarmor.ai/mcp"
    },
    "prompts_list": {
      "error": "Client error '401 Unauthorized' for url 'https://mcp.anomalyarmor.ai/mcp'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/401",
      "headers": {
        "content-type": "application/json",
        "www-authenticate": "Bearer error=\"invalid_token\", error_description=\"Authentication failed. The provided bearer token is invalid, expired, or no longer recognized by the server. To resolve: clear authentication tokens in your MCP client and reconnect. Your client should automatically re-register and obtain new tokens.\", resource_metadata=\"https://mcp.anomalyarmor.ai/.well-known/oauth-protected-resource/mcp\""
      },
      "http_status": 401,
      "payload": {},
      "reason": "auth_required",
      "url": "https://mcp.anomalyarmor.ai/mcp"
    },
    "resources_list": {
      "error": "Client error '401 Unauthorized' for url 'https://mcp.anomalyarmor.ai/mcp'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/401",
      "headers": {
        "content-type": "application/json",
        "www-authenticate": "Bearer error=\"invalid_token\", error_description=\"Authentication failed. The provided bearer token is invalid, expired, or no longer recognized by the server. To resolve: clear authentication tokens in your MCP client and reconnect. Your client should automatically re-register and obtain new tokens.\", resource_metadata=\"https://mcp.anomalyarmor.ai/.well-known/oauth-protected-resource/mcp\""
      },
      "http_status": 401,
      "payload": {},
      "reason": "auth_required",
      "url": "https://mcp.anomalyarmor.ai/mcp"
    },
    "tools_list": {
      "error": "Client error '401 Unauthorized' for url 'https://mcp.anomalyarmor.ai/mcp'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/401",
      "headers": {
        "content-type": "application/json",
        "www-authenticate": "Bearer error=\"invalid_token\", error_description=\"Authentication failed. The provided bearer token is invalid, expired, or no longer recognized by the server. To resolve: clear authentication tokens in your MCP client and reconnect. Your client should automatically re-register and obtain new tokens.\", resource_metadata=\"https://mcp.anomalyarmor.ai/.well-known/oauth-protected-resource/mcp\""
      },
      "http_status": 401,
      "payload": {},
      "url": "https://mcp.anomalyarmor.ai/mcp"
    },
    "transport_compliance_probe": {
      "bad_protocol_error": null,
      "bad_protocol_headers": {
        "content-type": "application/json",
        "www-authenticate": "Bearer error=\"invalid_token\", error_description=\"Authentication failed. The provided bearer token is invalid, expired, or no longer recognized by the server. To resolve: clear authentication tokens in your MCP client and reconnect. Your client should automatically re-register and obtain new tokens.\", resource_metadata=\"https://mcp.anomalyarmor.ai/.well-known/oauth-protected-resource/mcp\""
      },
      "bad_protocol_payload": {
        "error": "invalid_token",
        "error_description": "Authentication failed. The provided bearer token is invalid, expired, or no longer recognized by the server. To resolve: clear authentication tokens in your MCP client and reconnect. Your client should automatically re-register and obtain new tokens."
      },
      "bad_protocol_status_code": 401,
      "delete_error": null,
      "delete_status_code": null,
      "expired_session_error": null,
      "expired_session_status_code": null,
      "issues": [
        "missing_protocol_header",
        "bad_protocol_not_rejected"
      ],
      "last_event_id_visible": false,
      "protocol_header_present": false,
      "requested_protocol_version": "2025-03-26",
      "session_id_present": false,
      "transport": "streamable-http"
    }
  },
  "remote_url": "https://mcp.anomalyarmor.ai/mcp",
  "server_card_payload": {
    "$schema": "https://modelcontextprotocol.io/schemas/server-card/draft-1.json",
    "authentication": {
      "oauthProtectedResource": "https://mcp.anomalyarmor.ai/.well-known/oauth-protected-resource/mcp",
      "type": "oauth2"
    },
    "capabilities": {
      "prompts": {
        "listChanged": true
      },
      "resources": {
        "listChanged": true
      },
      "tools": {
        "categories": [
          "catalog",
          "destinations",
          "freshness",
          "alerts",
          "health",
          "recommendations",
          "intelligence"
        ],
        "listChanged": true
      }
    },
    "description": "Data observability tools for AI assistants. Query alerts, monitor freshness, inspect schema changes, and manage destinations via natural language.",
    "installation": {
      "claudeCode": "claude mcp add anomalyarmor --transport http https://mcp.anomalyarmor.ai/mcp",
      "cursor": {
        "mcpServers": {
          "anomalyarmor": {
            "url": "https://mcp.anomalyarmor.ai/mcp"
          }
        }
      },
      "local": {
        "args": [
          "armor-mcp"
        ],
        "command": "uvx",
        "env": {
          "ARMOR_API_KEY": "aa_live_your_key_here"
        }
      }
    },
    "name": "AnomalyArmor",
    "serverInfo": {
      "description": "Data observability tools for AI assistants. Query alerts, monitor freshness, inspect schema changes, and manage destinations via natural language.",
      "documentation": "https://docs.anomalyarmor.ai/integrations/mcp-server",
      "homepage": "https://www.anomalyarmor.ai",
      "name": "AnomalyArmor",
      "title": "AnomalyArmor MCP Server",
      "vendor": {
        "name": "AnomalyArmor",
        "supportEmail": "support@anomalyarmor.ai",
        "url": "https://www.anomalyarmor.ai"
      },
      "version": "0.7.0"
    },
    "serverUrl": "https://mcp.anomalyarmor.ai/mcp",
    "transports": [
      {
        "preferred": true,
        "type": "streamable-http",
        "url": "https://mcp.anomalyarmor.ai/mcp"
      }
    ],
    "version": "0.7.0"
  },
  "server_identifier": "ai.anomalyarmor/armor-mcp"
}

Known versions

0.6.1

Validation history

7 day score delta

n/a

30 day score delta

n/a

Recent healthy ratio

Freshness

0.4h

Timestamp	Status	Score	Latency
May 13, 2026 05:39:46 PM UTC	Failing	60.5	986.0 ms
May 13, 2026 09:32:04 AM UTC	Failing	60.2	585.7 ms
May 13, 2026 01:30:28 AM UTC	Failing	59.9	841.9 ms
May 12, 2026 05:28:57 PM UTC	Failing	59.8	872.0 ms
May 12, 2026 09:21:10 AM UTC	Failing	59.7	612.3 ms
May 12, 2026 01:20:21 AM UTC	Failing	56.0	611.8 ms

Validation timeline

Validated	Summary	Score	Protocol	Auth mode	Changes
May 13, 2026 05:39:46 PM UTC	Failing	60.5	unknown	oauth_required	none
May 13, 2026 09:32:04 AM UTC	Failing	60.2	unknown	oauth_required	none
May 13, 2026 01:30:28 AM UTC	Failing	59.9	unknown	oauth_required	none
May 12, 2026 05:28:57 PM UTC	Failing	59.8	unknown	oauth_required	none
May 12, 2026 09:21:10 AM UTC	Failing	59.7	unknown	oauth_required	none
May 12, 2026 01:20:21 AM UTC	Failing	56.0	unknown	oauth_required	none

Recent validation runs

Started	Status	Summary	Latency	Checks
May 13, 2026 05:39:45 PM UTC	Completed	Failing	986.0 ms	action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe
May 13, 2026 09:32:03 AM UTC	Completed	Failing	585.7 ms	action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe
May 13, 2026 01:30:28 AM UTC	Completed	Failing	841.9 ms	action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe
May 12, 2026 05:28:56 PM UTC	Completed	Failing	872.0 ms	action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe
May 12, 2026 09:21:09 AM UTC	Completed	Failing	612.3 ms	action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe
May 12, 2026 01:20:21 AM UTC	Completed	Failing	611.8 ms	action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe