← Back to search

Search • Rankings • TrustOps • Docs • Pricing • Claim/Manage

ai.meacheal/mrc-data

MRC Data — China's Apparel Supply Chain Infrastructure

China's apparel supply chain data for AI: 1,000+ suppliers, 350+ fabrics, 170+ clusters.

JSON report • Policy • Badge metadata • History API • • Global feed

DECISION SUMMARY

Block For Production

Score

n/a

Percentile pending

Confidence

High

Based on evidence completeness, recency, and validation density.

Evidence age

2.4h old

Freshness: fresh. Snapshot trustsnap_bd29047965fc63b3.

Top risk drivers

Trust Confidence
Tool Surface Design
Tool Snapshot Churn

Recommended actions

Make tools/list succeed unauthenticated when possible, or document the auth flow in the server card.
Fix the failing checks first, then revalidate to confirm the recovery path.
Compare tool enumeration outputs between runs and remove non-deterministic behavior.

Next action

revalidate, add safeguards, export policy

failing live status

Compare alternatives Export policy Open report JSON Dispute this assessment

Observed Attention

No observed attention

No observed attention in the current 30-day window.

No segmented attention signals observed in the current window.

Bucketed signal based on recent segmented Verify telemetry. Crawler and evaluator activity is not treated as confirmed human demand.

Risk Compatibility Evidence Fix it Governance

Status

Failing

Score

n/a

Transport

streamable-http

Tools

Ownership

Unclaimed

Claim, revalidate, or manage this server

DISPUTE THIS ASSESSMENT

Dispute this assessment

If any published claim about this server -- its score, a risk flag, a capability classification, or its taxonomy -- is factually wrong, tell us what evidence shows and we will review it. This does not require claiming or verifying ownership of the server first.

Verify responds to disputes within 5 business days and resolves them within 15.

Dispute history

No disputes filed for this server.

Risk

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

Not_Assessed

Safe to publish

✓

Auth boundary

public_or_unclear

Blast radius

Low

High-risk tools

Confirmation signals

none

Safeguard count

Status detail: No write-action governance evidence is available yet.

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.

Critical alerts

Production verdicts degrade quickly when critical alerts are active.

Compatibility

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

Not client-compatible

Confidence: high (76.25)

Evidence provenance

Winner: live_validation

Supporting sources: live_validation, history, server_card

Disagreements: none

initialize • OK
tools_list • Error
transport_compliance_probe • Error
step_up_auth_probe • Missing
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: high (76.25)

Evidence provenance

Winner: live_validation

Supporting sources: live_validation, history, server_card

Disagreements: none

initialize • OK
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: high (76.25)

Evidence provenance

Winner: live_validation

Supporting sources: live_validation, history

Disagreements: none

action_safety_probe • Not_Assessed

Snapshot churn risk

Low

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

Confidence: high (76.25)

Evidence provenance

Winner: history

Supporting sources: history, live_validation

Disagreements: none

tool_snapshot_probe • Missing
connector_replay_probe • Missing

Client compatibility gate details

ChatGPT custom connector

Not client-compatible

Remediation checklist

OpenAI connectors expect OAuth for remote server auth.
Dynamic client registration materially improves connector setup.
tools/list must succeed.
Transport compliance should be in good shape.
OAuth interoperability should be strong.
The tool surface is not limited to search/fetch-style read tools.

Claude remote MCP

Not client-compatible

Remediation checklist

tools/list must succeed.
Transport behavior should match Claude-compatible HTTP expectations.
A useful Claude integration needs at least one exposed tool.
The tool surface is not limited to search/fetch-style read tools.
OAuth is not configured, so this client cannot authenticate without additional setup.
Not yet safe for company-knowledge use: requires a search/fetch-only surface with no write actions present.

Write-safe publishing

Ready

Remediation checklist

No explicit blockers recorded.

Verdict traces

Production verdict

Metadata only

No live validation evidence exists yet for this entry.

Confidence: high (76.25)

Winning source: live_validation

Triggering alerts

server_failing • critical • Latest validation is failing
tools_list_regressed • critical • tools/list regressed
auth_mode_changed • high • Auth mode changed

Client verdict trace table

Verdict	Status	Checks	Winning source	Conflicts
`openai_connectors`	Not 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

OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.; tools/list must succeed.; Transport compliance should be in good shape.; OAuth interoperability should be strong. Compatibility is not a production approval; company knowledge and Messages API gates remain separate.

Search Fetch Only: No
Write Actions Present: No
Oauth Configured: No
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: No
Admin Refresh Required: No
Safe For Company Knowledge: No
Safe For Messages Api Remote Mcp: No

Compatibility fixtures

ChatGPT custom connector fixture

Degraded

remote_http_endpoint: Passes
oauth_discovery: Degraded
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

Recommended for

No recommendation profile is available yet.

Evidence

Current trust snapshot

Snapshot ID

trustsnap_bd29047965fc63b3

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

Snapshot generated

Aug 06, 2026 09:39:35 AM UTC

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

Last validated

Aug 06, 2026 07:17:16 AM UTC

Age: 2.37h • evidence age tier: Verified in last 24h • display score: suppressed

Canonical machine links

Compare index

/compare.json

Compare API

/v1/compare?server=ai.meacheal%2Fmrc-data

Trust summary

/v1/servers/ai.meacheal/mrc-data/trust-summary

Report JSON

/v1/servers/ai.meacheal/mrc-data/report

Policy export

/v1/servers/ai.meacheal/mrc-data/policy

Badge metadata

/v1/servers/ai.meacheal/mrc-data/badge

Ledger evidence

/v1/servers/ai.meacheal/mrc-data/ledger

Human compare URL

/compare?server=ai.meacheal%2Fmrc-data

Evidence confidence

Confidence score

76.2

Based on 9 recent validations, 27 captured checks, and validation age of 2.4 hours.

Live checks captured

More direct checks increase trust in the current verdict.

Validation age

2.4h

Lower age means fresher evidence.

Latest validation evidence

Latest summary

Failing

Validation profile

remote_mcp

Started

Aug 06, 2026 07:17:13 AM UTC

Latency

2958.3 ms

Failures

oauth_authorization_server no authorization server
oauth_protected_resource Client error '404 Not Found' for url 'https://api.meacheal.ai/.well-known/oauth-protected-resource' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404
openid_configuration no authorization server
prompts_list Client error '400 Bad Request' for url 'https://api.meacheal.ai/mcp' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400
resources_list Client error '400 Bad Request' for url 'https://api.meacheal.ai/mcp' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400
tools_list Client error '400 Bad Request' for url 'https://api.meacheal.ai/mcp' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400
transport_compliance_probe Issues: missing protocol header, bad protocol not rejected, delete session unexpected, expired session not 404 (bad protocol=200, DELETE=401, expired session=200).

Checks

Check	Status	Latency	Evidence
`action_safety_probe`	Not_Assessed	n/a	No write-action risk evidence recorded.
`advanced_capabilities_probe`	Warning	n/a	Only 3 capability signal(s): prompts, resource links, resources.
`connector_publishability_probe`	Error	n/a	Publishability blockers: tools list, transport compliance, action safety, tool surface.
`connector_replay_probe`	Missing	n/a	No connector replay evidence recorded.
`determinism_probe`	Missing	n/a	tools list unavailable
`initialize`	OK	884.6 ms	Protocol 2025-03-26
`interactive_flow_probe`	Missing	n/a	Check completed
`oauth_authorization_server`	Missing	n/a	no authorization server
`oauth_protected_resource`	Error	30.2 ms	Client error '404 Not Found' for url 'https://api.meacheal.ai/.well-known/oauth-protected-resource' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404
`official_registry_probe`	OK	n/a	Check completed
`openid_configuration`	Missing	n/a	no authorization server
`probe_noise_resilience`	OK	279.0 ms	Fetched https://api.meacheal.ai/robots.txt
`prompt_get`	Missing	n/a	no prompt name
`prompts_list`	Error	82.8 ms	Client error '400 Bad Request' for url 'https://api.meacheal.ai/mcp' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400
`protocol_version_probe`	Warning	n/a	Claims 2025-03-26; 2 release(s) behind 2025-11-25.
`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`	Error	326.5 ms	Client error '400 Bad Request' for url 'https://api.meacheal.ai/mcp' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400
`schema_divergence_probe`	Missing	n/a	no live tools
`server_card`	OK	195.6 ms	3 prompt(s) exposed
`session_resume_probe`	OK	63.6 ms	20 tool(s) exposed
`step_up_auth_probe`	Missing	n/a	No OAuth or incremental-scope signals detected.
`tool_snapshot_probe`	Missing	n/a	no tools
`tools_list`	Error	396.4 ms	Client error '400 Bad Request' for url 'https://api.meacheal.ai/mcp' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400
`transport_compliance_probe`	Error	150.4 ms	Issues: missing protocol header, bad protocol not rejected, delete session unexpected, expired session not 404 (bad protocol=200, DELETE=401, expired session=200).
`utility_coverage_probe`	OK	25.4 ms	No completions evidence; no pagination evidence; tasks auth required.

Raw evidence view

Show raw JSON evidence

Large evidence payload summarized to keep this page fast. Full raw evidence remains available from the JSON report.

{
  "checks": {
    "count": 27,
    "items": {
      "action_safety_probe": {
        "auth_present": false,
        "reason": "empty_observation_set",
        "safeguard_count": 0,
        "status": "not_assessed"
      },
      "advanced_capabilities_probe": {
        "status": "warning"
      },
      "connector_publishability_probe": {
        "status": "error"
      },
      "connector_replay_probe": {
        "reason": "no_tools",
        "status": "missing"
      },
      "determinism_probe": {
        "reason": "tools_list_unavailable",
        "status": "missing"
      },
      "initialize": {
        "http_status": 200,
        "latency_ms": 884.62,
        "payload_omitted": true,
        "status": "ok"
      },
      "interactive_flow_probe": {
        "status": "missing"
      },
      "oauth_authorization_server": {
        "reason": "no_authorization_server",
        "status": "missing"
      },
      "oauth_protected_resource": {
        "latency_ms": 30.23,
        "reason": "Client error '404 Not Found' for url 'https://api.meacheal.ai/.well-known/oauth-protected-resource'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
        "status": "error"
      },
      "official_registry_probe": {
        "status": "ok"
      },
      "openid_configuration": {
        "reason": "no_authorization_server",
        "status": "missing"
      },
      "probe_noise_resilience": {
        "http_status": 200,
        "latency_ms": 278.98,
        "status": "ok"
      },
      "prompt_get": {
        "reason": "no_prompt_name",
        "status": "missing"
      },
      "prompts_list": {
        "http_status": 400,
        "latency_ms": 82.82,
        "payload_omitted": true,
        "reason": "Client error '400 Bad Request' for url 'https://api.meacheal.ai/mcp'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400",
        "status": "error"
      },
      "protocol_version_probe": {
        "status": "warning"
      },
      "provenance_divergence_probe": {
        "status": "ok"
      },
      "request_association_probe": {
        "reason": "no_request_association_capabilities_advertised",
        "status": "missing"
      },
      "resource_read": {
        "reason": "no_resource_uri",
        "status": "missing"
      },
      "resources_list": {
        "http_status": 400,
        "latency_ms": 326.5,
        "payload_omitted": true,
        "reason": "Client error '400 Bad Request' for url 'https://api.meacheal.ai/mcp'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400",
        "status": "error"
      },
      "schema_divergence_probe": {
        "reason": "no_live_tools",
        "status": "missing"
      },
      "server_card": {
        "http_status": 200,
        "latency_ms": 195.64,
        "payload_omitted": true,
        "status": "ok",
        "tool_count": 19,
        "tool_names_preview": [
          "search_suppliers",
          "get_supplier_detail",
          "search_fabrics",
          "get_fabric_detail",
          "search_clusters",
          "compare_clusters",
          "detect_discrepancy",
          "get_supplier_fabrics",
          "get_fabric_suppliers",
          "get_product_categories",
          "get_province_distribution",
          "recommend_suppliers",
          "analyze_market",
          "estimate_cost",
          "check_compliance",
          "find_alternatives",
          "compare_suppliers",
          "get_cluster_suppliers",
          "get_stats"
        ]
      },
      "session_resume_probe": {
        "http_status": 200,
        "latency_ms": 63.64,
        "payload_omitted": true,
        "status": "ok",
        "tool_count": 20,
        "tool_names_preview": [
          "search_suppliers",
          "get_supplier_detail",
          "search_fabrics",
          "get_fabric_detail",
          "search_clusters",
          "compare_clusters",
          "detect_discrepancy",
          "get_supplier_fabrics",
          "get_fabric_suppliers",
          "get_product_categories",
          "get_province_distribution",
          "recommend_suppliers",
          "analyze_market",
          "estimate_cost",
          "check_compliance",
          "assess_supplier_credibility",
          "find_alternatives",
          "compare_suppliers",
          "get_cluster_suppliers",
          "get_stats"
        ]
      },
      "step_up_auth_probe": {
        "status": "missing"
      },
      "tool_snapshot_probe": {
        "reason": "no_tools",
        "status": "missing"
      },
      "tools_list": {
        "http_status": 400,
        "latency_ms": 396.36,
        "payload_omitted": true,
        "reason": "Client error '400 Bad Request' for url 'https://api.meacheal.ai/mcp'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400",
        "status": "error"
      },
      "transport_compliance_probe": {
        "latency_ms": 150.45,
        "protocol_header_present": false,
        "status": "error"
      },
      "utility_coverage_probe": {
        "latency_ms": 25.37,
        "status": "ok"
      }
    },
    "omitted_count": 0
  },
  "failures": {
    "count": 7,
    "items": {
      "oauth_authorization_server": {},
      "oauth_protected_resource": {},
      "openid_configuration": {},
      "prompts_list": {},
      "resources_list": {},
      "tools_list": {},
      "transport_compliance_probe": {}
    },
    "omitted_count": 0
  },
  "message": "Raw evidence is summarized in HTML to keep server detail pages fast. Use the JSON report or evidence API for the full payload.",
  "remote_url": "https://api.meacheal.ai/mcp",
  "server_card": {
    "name": "MRC Data",
    "raw_payload_omitted": true,
    "version": "2.2.2"
  },
  "server_identifier": "ai.meacheal/mrc-data",
  "truncated": true
}

Known versions

2.2.2

Validation history

7 day score delta

n/a

30 day score delta

n/a

Recent healthy ratio

Freshness

2.4h

Timestamp	Status	Score	Latency
Aug 06, 2026 07:17:16 AM UTC	Failing	6.4	2958.3 ms
Aug 05, 2026 11:16:55 PM UTC	Failing	7.4	3492.7 ms
Aug 05, 2026 07:16:31 PM UTC	Failing	14.2	3475.1 ms
Aug 03, 2026 10:12:06 AM UTC	Failing	21.4	3081.4 ms
Aug 02, 2026 06:24:40 PM UTC	Failing	21.2	3777.7 ms
Aug 02, 2026 03:58:09 AM UTC	Failing	21.1	3343.7 ms
Aug 01, 2026 01:09:01 PM UTC	Failing	21.0	3441.0 ms
Jul 31, 2026 09:54:24 PM UTC	Failing	20.9	4193.6 ms

Validation timeline

Validated	Summary	Score	Protocol	Auth mode	Changes
Aug 06, 2026 07:17:16 AM UTC	Failing	6.4	2025-03-26	public	auth_mode_changed
Aug 05, 2026 11:16:55 PM UTC	Failing	7.4	unknown	unknown	none
Aug 05, 2026 07:16:31 PM UTC	Failing	14.2	unknown	unknown	none
Aug 03, 2026 10:12:06 AM UTC	Failing	21.4	unknown	unknown	none
Aug 02, 2026 06:24:40 PM UTC	Failing	21.2	unknown	unknown	none
Aug 02, 2026 03:58:09 AM UTC	Failing	21.1	unknown	unknown	none
Aug 01, 2026 01:09:01 PM UTC	Failing	21.0	unknown	unknown	none
Jul 31, 2026 09:54:24 PM UTC	Failing	20.9	unknown	unknown	none
Jul 31, 2026 06:39:26 AM UTC	Failing	21.1	unknown	unknown	none

Recent validation runs

Recent validation runs for this MCP server
Started	Status	Summary	Latency	Checks
Aug 06, 2026 07:17:13 AM UTC	Completed	Failing	2958.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, schema_divergence_probe, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe
Aug 05, 2026 11:16:52 PM UTC	Completed	Failing	3492.7 ms
Aug 05, 2026 07:16:27 PM UTC	Completed	Failing	3475.1 ms
Aug 03, 2026 10:12:03 AM UTC	Completed	Failing	3081.4 ms
Aug 02, 2026 06:24:36 PM UTC	Completed	Failing	3777.7 ms
Aug 02, 2026 03:58:06 AM UTC	Completed	Failing	3343.7 ms
Aug 01, 2026 01:08:57 PM UTC	Completed	Failing	3441.0 ms
Jul 31, 2026 09:54:20 PM UTC	Completed	Failing	4193.6 ms
Jul 31, 2026 06:39:23 AM UTC	Completed	Failing	2851.6 ms

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
Aug 05, 2026 11:00:35 AM UTC	Score corrected (post-1.0.503 remediation, R1 zero-anchoring)	Prior: 21.43. Corrected: 13.55.
Aug 06, 2026 07:17:16 AM UTC	Latest validation: failing	Score 10.7 with status failing.
Aug 06, 2026 07:17:16 AM UTC	Score changed	Score delta -0.9 versus the previous run.
Aug 06, 2026 07:17:16 AM UTC	Auth mode changed	Auth mode moved from unknown to public.
Aug 05, 2026 11:16:55 PM UTC	Score changed	Score delta -6.8 versus the previous run.
Aug 05, 2026 07:16:31 PM UTC	Score changed	Score delta -7.2 versus the previous run.

Capabilities

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

Use-case taxonomy

other

Benchmark tasks

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

Utility coverage

Probe status

Completions

not detected

Completion probe target: { "type": "resource", "uri": "mrc://overview" }

Pagination

not detected

No nextCursor evidence.

Tasks

Auth Required

Advertised: no

Transport compliance drilldown

Probe status

Error

Transport

streamable-http

Session header

yes

Protocol header

Bad protocol response

200

DELETE teardown

401

Expired session retry

200

Last-Event-ID visible

Issues: missing_protocol_header, bad_protocol_not_rejected, delete_session_unexpected, expired_session_not_404

Request association

Status

Missing

Advertised capabilities

none

Observed idle methods

none

Violating methods

none

Probe HTTP status

n/a

Issues

none

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.

Tool snapshot diff & changelog

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

Validation diff

Score delta

-0.94

Summary changed

Tool delta

Prompt delta

Auth mode changed

yes

Write surface expanded

Protocol regressed

Registry drift changed

Regressed checks: action_safety_probe, connector_publishability_probe, oauth_protected_resource, prompts_list, resources_list, tools_list, transport_compliance_probe

Improved checks: initialize, official_registry_probe, probe_noise_resilience, provenance_divergence_probe, server_card, session_resume_probe, utility_coverage_probe

Newly assessed dimensions: none

No longer assessed dimensions: none

Component	Previous	Latest	Delta
`oauth_interop_score`	3.0	0.0	-3.0

Registry & provenance divergence

Probe status

Direct official match

yes

Drift fields

none

Field	Registry	Live server card
Title	n/a	MRC Data
Version	n/a	2.2.2
Homepage	n/a	https://api.meacheal.ai

Active alerts

Latest validation is failing (critical)
Core MCP flows did not validate successfully on the latest run.
tools/list regressed (critical)
Tool discovery became less reliable on the latest run.
Auth mode changed (high)
Auth mode changed from unknown to public.

Aliases & registry graph

Identifier	Source	Canonical	Score
`ai.meacheal/mrc-data`	official_registry	yes	6.4

Alias consolidation

Canonical identifier

ai.meacheal/mrc-data

Duplicate aliases

Registry sources

official_registry

Remote URLs

https://api.meacheal.ai/mcp

Homepages

https://api.meacheal.ai

Source disagreements

Field	What differs	Observed values
No source disagreements detected.

Fix it

Why this score?

Access & Protocol

15/44

Connectivity, auth, and transport expectations for common clients.

Interface Quality

9/56

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

Security Posture

6/36

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

Reliability & Trust

6/24

Operational stability, consistency, and trustworthiness over time.

Discovery & Governance

18/28

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

Adoption & Market

5/8

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

Algorithmic score breakdown

Auth Operability

2/4

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

Error Contract Quality

0/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

0/4

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

Security Hygiene

2/4

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

Task Success

0/4

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

Trust Confidence

0/4

Confidence-adjusted reliability score that penalizes low evidence volume.

Abuse/Noise Resilience

1/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

3/4

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

Discovery Metadata

2/4

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

Registry Consistency

2/4

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

Installability

1/4

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

Session Semantics

1/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

0/4

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

Recovery Semantics

0/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

3/4

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

Freshness Confidence

1/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

4/4

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

Step-Up Auth

0/4

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

Transport Compliance

1/4

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

Utility Coverage

1/4

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

Advanced Capability Coverage

1/4

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

Connector Publishability

2/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

0/4

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

Request Association

0/4

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

Interactive Flow Safety

0/4

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

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

1/4

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

Egress / SSRF Resilience

1/4

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

Execution / Sandbox Safety

1/4

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

Data Exfiltration Resilience

0/4

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

Least Privilege Scope

1/4

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

Secret Handling Hygiene

1/4

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

Supply Chain Signal

1/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.

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	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.
Critical	Respond to tools/list regressed	Tool discovery became less reliable on the latest run.	Compare tool enumeration outputs between runs and remove non-deterministic behavior.
High	Add confirmation and dry-run semantics for risky actions	High-risk write, delete, exec, or egress tools should communicate safeguards clearly.	Add an explicit confirm/dry-run parameter or two-step confirmation flow to write, delete, exec, and egress-capable tools before they can make destructive changes. Playbook For each high-risk tool (delete, exec, or network-egress capable), add a `confirm`/`dry_run` parameter or a two-step confirmation flow. Document the safeguard in the tool's description so clients and agents know confirmation is required before execution. Revalidate and confirm `action_safety_probe` reports the safeguard as detected.
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.	Only send roots/list, sampling/createMessage, or elicitation/create requests while handling an active client-initiated request, never on idle sessions. Playbook Only send `roots/list`, `sampling/createMessage`, or `elicitation/create` requests while handling an active client-initiated request. Avoid emitting these requests on idle or newly-initialized sessions with no pending client request. Revalidate and confirm `request_association_probe` no longer returns `missing` or `warning`.
High	Expose /.well-known/oauth-protected-resource	Without a protected-resource document, OAuth clients cannot discover auth requirements reliably.	Serve /.well-known/oauth-protected-resource and point it at your authorization server metadata. Playbook Serve `/.well-known/oauth-protected-resource` from the same host as the MCP endpoint. Point it at the authorization server metadata URL. Confirm clients receive consistent auth hints before tool execution.
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.	Avoid removing tools, adding new required arguments, or changing outputSchema for tools already published to connector directories without a version bump. Playbook Avoid removing tools or adding new required arguments to existing tools without a major version bump. Avoid breaking changes to `outputSchema` for tools already published to connector directories. This check reads `no_historical_snapshot` on a server's first validation run -- that is expected, not itself a defect, and resolves after a second run.
High	Publish OAuth authorization-server metadata	Clients need authorization-server metadata to discover issuer, endpoints, and DCR support.	Publish /.well-known/oauth-authorization-server from your issuer and include registration_endpoint when supported. Playbook Publish `/.well-known/oauth-authorization-server` from the issuer. Add `registration_endpoint` if DCR is supported. Verify issuer, authorization, token, and jwks metadata are all reachable.
High	Respond to auth mode changed	Auth mode changed from unknown to public.	Document the new auth posture and confirm protected-resource and challenge metadata still match reality.
High	Stop asking users to paste secrets directly	Public MCP servers should prefer OAuth or browser-based auth guidance over in-band secret collection.
High	Sync the published server card's tool schemas with the live tool surface	The server card and live tools/list disagree on parameter names, required sets, or types -- clients that trust the published card will construct invalid calls.	Regenerate the published server card from the live tool schemas (or vice versa) so parameter names, required sets, and types match exactly. Playbook Diff the published `/.well-known/mcp/server-card.json` tool schemas against a live `tools/list` response. Fix parameter name mismatches, required-set mismatches, and type mismatches per tool. Regenerate or hand-sync the server card whenever the live tool schemas change -- treat drift as a release blocker, not a documentation nit.
Medium	Adopt a current MCP protocol revision	Older protocol revisions reduce compatibility with newer clients and registry programs.	Advertise a current MCP protocol revision (2025-06-18 or later) in both the initialize response and the MCP-Protocol-Version header. Playbook Update the server's advertised protocol version to a current MCP revision (2025-06-18 or later). Return the negotiated version consistently in both the `initialize` response and the `MCP-Protocol-Version` header. Revalidate and confirm `protocol_version_probe` reports `ok`.
Medium	Close connector-publishing gaps	Connector catalogs care about protocol recency, session behavior, auth clarity, and tool-surface stability.
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	Publish OpenID configuration	OIDC metadata improves token validation and client compatibility.	Expose /.well-known/openid-configuration with issuer, jwks_uri, and supported grants. Playbook Serve `/.well-known/openid-configuration` with `issuer`, `jwks_uri`, `authorization_endpoint`, and `token_endpoint`. List supported grant types in `grant_types_supported` and scopes in `scopes_supported`. Revalidate and confirm the `openid_configuration` check returns `ok`.
Medium	Raise Access & Protocol score	Connectivity, auth, and transport expectations for common clients.	Tighten auth discovery, session behavior, and transport metadata until remote clients can connect without guesswork.
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.
Medium	Raise Reliability & Trust score	Operational stability, consistency, and trustworthiness over time.	Stabilize behavior over time and reduce failure drift between validation runs.
Medium	Raise Security Posture score	How safely the exposed tool surface handles destructive actions, egress, execution, secrets, and risky inputs.	Reduce destructive, egress, exec, secret, and freeform-input risk across the exposed tool surface. Playbook Classify each tool by read/write/delete/exec/network capability and confirm the classification is intentional. Gate high-risk tools behind scoped auth, narrow their schemas, and document safeguards such as allowlists or dry-run paths. Revalidate after the risky tools are tightened so the security posture score reflects the current surface.
Medium	Reduce tool-surface churn	Frequent add/remove or output-shape drift makes published connectors and cached tool snapshots brittle.	Keep tool names, required arguments, and output schemas stable between deploys, and publish a changelog entry when they must change. Playbook Avoid changing tool names, required arguments, or output schemas between deploys unless the change is intentional. Publish a changelog entry when the tool surface changes so cached or frozen client snapshots can be reconciled. This check compares against the previous run, so it needs a second validation before it can report a stable baseline.
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.
Low	Publish newer MCP capability signals	Roots, sampling, elicitation, structured outputs, and related metadata improve client understanding and ranking.	Advertise only the advanced capabilities (roots, sampling, elicitation) you have actually implemented end to end in the initialize capabilities object. Playbook Add the capabilities you actually support (`roots`, `sampling`, `elicitation`) to the `capabilities` object returned from `initialize`. Only advertise a capability once the corresponding request/response flow is implemented end to end. Revalidate and confirm `advanced_capabilities_probe` reflects the updated capability set.

Point loss breakdown

Component	Current	Points missing
Trust Confidence	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
Task Success	0/4	-4.0
Step Up Auth	0/4	-4.0
SLO Health	0/4	-4.0
Schema Completeness	0/4	-4.0
Result Shape Stability	0/4	-4.0
Request Association	0/4	-4.0
Recovery Semantics	0/4	-4.0

Compatibility profiles

OpenAI Connectors

44.4

blocked

Connector URL: https://api.meacheal.ai/mcp
# No OAuth metadata detected.
# Server: ai.meacheal/mrc-data

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": {
    "mrc-data": {
      "command": "npx",
      "args": ["mcp-remote", "https://api.meacheal.ai/mcp"]
    }
  }
}

Smithery

60.0

partial

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

smithery mcp add "https://api.meacheal.ai/mcp"

Generic Streamable HTTP

66.7

partial

tools/list must succeed.; Session behavior should be predictable.

curl -sS https://api.meacheal.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"}}}'

Governance

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.

Evidence age tier

Verified in last 24h

Policy SLA (contractual, distinct from the public 24h freshness window): 168.0h • confidence-weighted score (display score discounted for evidence age and confidence -- an internal TrustOps input, not the public score): n/a • evidence too old to display: ✕

Policy exports

Export policy

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

Runtime routing

/v1/decide

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

Hosted runtime

Verify Hosted MCP

Deploy trusted servers from GitHub with secrets, egress controls, releases, rollback, and audit events.

Authenticated validation

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

Active trust badges

Freshly Validated 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

MCP Runtime hosting

Verify Hosted MCP turns a trusted server report into a managed remote MCP endpoint with GitHub deployment provenance, sandbox policy, encrypted secrets, release history, rollback, and audit/usage events.

Activation readiness

Trusted hosted runtimes require fresh validation, a passing server state, a remote endpoint, and a minimum score.

Minimum tier

TrustOps

Publisher claim plus paid TrustOps tier are required before secrets or releases can be created.

Hosted endpoint

/hosted/{namespace}/{name}/mcp

The endpoint enforces egress allowlists and records audit/usage events.

Blockers

score_below_hosting_threshold server_not_healthy_or_degraded latest_validation_not_passing

Deployment	Status	Endpoint	Release
No hosted runtime deployments yet.

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

Install snippets

Openai Connectors

Connector URL: https://api.meacheal.ai/mcp
# No OAuth metadata detected.
# Server: ai.meacheal/mrc-data

Claude Desktop

{
  "mcpServers": {
    "mrc-data": {
      "command": "npx",
      "args": ["mcp-remote", "https://api.meacheal.ai/mcp"]
    }
  }
}

Smithery

smithery mcp add "https://api.meacheal.ai/mcp"

Generic Http

curl -sS https://api.meacheal.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://api.meacheal.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.meacheal/mrc-data.

Direct machine links

JSON report • Compare this server • Verify MCP API