← Back to search
Search • Governance: TrustOps / Gateway / Compare • Publishers: Claim / Badges / Profiles • Research: Trust Index / Rankings • Docs: Methodology / Security / MCP API • Pricing • Claim/Manage
ai.agentlookups/overassessed

ai.agentlookups/overassessed

Maryland property-assessment fairness checks vs similar homes, with appeal windows and links.

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

Allow With Approval

Score
69.5
Top 1.0% of 75,287 scored public servers
Confidence
High
Based on evidence completeness, recency, and validation density.
Evidence age
43m old
Freshness: fresh. Snapshot trustsnap_684fbf7f430247ef.
Top risk drivers
  • Transport Compliance
  • Recovery Semantics
  • Advanced Capability Coverage
Recommended actions
  • Align MCP-Protocol-Version, MCP-Session-Id, DELETE teardown, and expired-session handling with the transport spec.
  • Only send roots/list, sampling/createMessage, or elicitation/create requests while handling an active client-initiated…
  • Serve /.well-known/oauth-protected-resource and point it at your authorization server metadata.
Next action
export policy, require approval for writes, add authenticated validation
write/admin actions need confirmation safeguards
Compare alternatives Export policy Open report JSON
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
Healthy
Score
69.5
Transport
streamable-http
Tools
1
Ownership
Unclaimed
Claim, revalidate, or manage this server

Risk

Security posture
Tools analyzed
1
High-risk tools
0
Destructive tools
0
Exec tools
0
Egress tools
0
Secret tools
0
Bulk-access tools
0
Risk distribution
medium:1
Tool capability & risk inventory
ToolCapabilitiesRiskFindingsNotes
check_assessment read write Medium none No explicit safeguard hints detected.
Write-action governance
Governance status
OK
Safe to publish
✓
Auth boundary
public_or_unclear
Blast radius
Low
High-risk tools
0
Confirmation signals
none
Safeguard count
0

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

ToolRiskFlagsSafeguards
No high-risk tools were detected on the latest run.
Action-controls diff
Snapshot changed
no
Disabled-by-default candidates
none
Manual review candidates
none
New actions
ActionRiskFlags
No newly added actions.
Changed actions
ActionChange typesRisk
No materially changed actions.
Critical alerts
Critical alerts
0
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
Partially client-compatible
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.; Transport compliance should be in good shape.
Confidence: high (76.25)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history, server_card
Disagreements: none
  • initialize • OK
  • tools_list • OK
  • 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
Client-compatible
Transport behavior should match Claude-compatible HTTP expectations.
Confidence: high (76.25)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history, server_card
Disagreements: none
  • initialize • OK
  • tools_list • OK
  • 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 • OK
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
Partially client-compatible
Remediation checklist
  • OpenAI connectors expect OAuth for remote server auth.
  • Dynamic client registration materially improves connector setup.
  • Transport compliance should be in good shape.
  • OAuth is not configured, so this client cannot authenticate without additional setup.
  • Not yet safe for the Messages API remote MCP path: requires OAuth, a compatible connector profile, and no pending connector-refresh risk.
  • Transport compliance issues should be resolved before wider client rollout.
Claude remote MCP
Client-compatible
Remediation checklist
  • Transport behavior should match Claude-compatible HTTP expectations.
  • OAuth is not configured, so this client cannot authenticate without additional setup.
  • Not yet safe for the Messages API remote MCP path: requires OAuth, a compatible connector profile, and no pending connector-refresh risk.
  • Transport compliance issues should be resolved before wider client rollout.
Write-safe publishing
Ready
Remediation checklist
  • No explicit blockers recorded.
Verdict traces
Production verdict
Safe for evaluation
The server is suitable for evaluation, but remaining gaps should be resolved before broad production use.
Confidence: high (76.25)
Winning source: live_validation
Triggering alerts
  • No active alert triggers.
Client verdict trace table
VerdictStatusChecksWinning sourceConflicts
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 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.; Transport compliance should be in good shape. Compatibility is not a production approval; company knowledge and Messages API gates remain separate.
  • Search Fetch Only: Yes
  • Write Actions Present: No
  • Oauth Configured: No
  • Admin Refresh Required: No
  • Safe For Company Knowledge: Yes
  • Safe For Messages Api Remote Mcp: No
Claude remote MCP compatibility
Connector-compatible
Transport behavior should match Claude-compatible HTTP expectations. Compatibility is not a production approval; company knowledge and Messages API gates remain separate.
  • Search Fetch Only: Yes
  • Write Actions Present: No
  • Oauth Configured: No
  • Admin Refresh Required: No
  • Safe For Company Knowledge: Yes
  • Safe For Messages Api Remote Mcp: No
Compatibility fixtures
ChatGPT custom connector fixture
Degraded
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.; Transport compliance should be in good shape.
  • remote_http_endpoint: Passes
  • oauth_discovery: Degraded
  • frozen_tool_snapshot_refresh: Passes
  • request_association: Passes
Anthropic remote MCP fixture
Degraded
Transport behavior should match Claude-compatible HTTP expectations.
  • remote_transport: Passes
  • tool_discovery: Passes
  • auth_connect: Passes
  • safe_write_review: Passes
Recommended for
Claude Desktop
Claude Desktop is marked compatible with score 83.
Smithery
Smithery is marked compatible with score 100.
Generic Streamable HTTP
Generic Streamable HTTP is marked compatible with score 100.
Agent Commerce & Payment Readiness

Agent Commerce & Payment Readiness - Beta

Commerce signal is weak and payment capability is none -- below the bar for a full commerce assessment on this page.

Evidence

Current trust snapshot
Snapshot ID
trustsnap_684fbf7f430247ef
Use this ID to compare server page, report, policy, MCP, homepage, ranking, and shortlist surfaces.
Snapshot generated
Aug 05, 2026 02:43:23 AM UTC
All page, report, policy, and MCP surfaces use this same server-detail snapshot shape.
Last validated
Aug 05, 2026 02:00:09 AM UTC
Age: 0.72h • evidence age tier: Verified in last 24h • display score: 69.46

Canonical machine links

Compare index
/compare.json
Compare API
/v1/compare?server=ai.agentlookups%2Foverassessed
Trust summary
/v1/servers/ai.agentlookups/overassessed/trust-summary
Report JSON
/v1/servers/ai.agentlookups/overassessed/report
Policy export
/v1/servers/ai.agentlookups/overassessed/policy
Badge metadata
/v1/servers/ai.agentlookups/overassessed/badge
Ledger evidence
/v1/servers/ai.agentlookups/overassessed/ledger
Human compare URL
/compare?server=ai.agentlookups%2Foverassessed
Evidence confidence
Confidence score
76.2
Based on 1 recent validations, 26 captured checks, and validation age of 0.7 hours.
Live checks captured
26
More direct checks increase trust in the current verdict.
Validation age
0.7h
Lower age means fresher evidence.
Latest validation evidence
Latest summary
Healthy
Validation profile
remote_mcp
Started
Aug 05, 2026 02:00:09 AM UTC
Latency
306.4 ms

Failures

  • oauth_authorization_server no authorization server
  • oauth_protected_resource Client error '404 Not Found' for url 'https://overassessed.agentlookups.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
  • server_card Client error '404 Not Found' for url 'https://overassessed.agentlookups.ai/.well-known/mcp/server-card.json' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404
  • transport_compliance_probe Issues: missing session id, missing protocol header, bad protocol not rejected (bad protocol=200).

Checks

CheckStatusLatencyEvidence
action_safety_probe OK n/a No high-risk write, destructive, or exec tools detected.
advanced_capabilities_probe Missing n/a No advanced MCP capability signals detected.
connector_publishability_probe Warning n/a Publishability blockers: transport compliance, server card.
connector_replay_probe Missing n/a No connector replay evidence recorded.
determinism_probe OK 16.0 ms Check completed
initialize OK 47.4 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 61.7 ms Client error '404 Not Found' for url 'https://overassessed.agentlookups.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 15.9 ms Fetched https://overassessed.agentlookups.ai/robots.txt
prompt_get Missing n/a not advertised
prompts_list Missing 15.2 ms not supported
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 not advertised
resources_list Missing 16.6 ms not supported
server_card Error 64.6 ms Client error '404 Not Found' for url 'https://overassessed.agentlookups.ai/.well-known/mcp/server-card.json' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404
session_resume_probe Warning n/a no session id
step_up_auth_probe Missing n/a No OAuth or incremental-scope signals detected.
tool_snapshot_probe Missing n/a no historical snapshot
tools_list OK 15.7 ms 1 tool(s) exposed
transport_compliance_probe Error 15.3 ms Issues: missing session id, missing protocol header, bad protocol not rejected (bad protocol=200).
utility_coverage_probe Missing 15.8 ms No completions evidence; no pagination evidence; tasks missing.
Raw evidence view
Show raw JSON evidence 
{
  "checks": {
    "action_safety_probe": {
      "details": {
        "auth_present": false,
        "confirmation_signals": [],
        "safeguard_count": 0,
        "summary": {
          "bulk_access_tools": 0,
          "capability_distribution": {
            "read": 1,
            "write": 1
          },
          "destructive_tools": 0,
          "egress_tools": 0,
          "exec_tools": 0,
          "high_risk_tools": 0,
          "risk_distribution": {
            "critical": 0,
            "high": 0,
            "low": 0,
            "medium": 1
          },
          "secret_tools": 0,
          "tool_count": 1
        }
      },
      "latency_ms": null,
      "status": "ok"
    },
    "advanced_capabilities_probe": {
      "details": {
        "capabilities": {
          "completions": false,
          "elicitation": false,
          "prompts": false,
          "resource_links": false,
          "resources": false,
          "roots": false,
          "sampling": false,
          "structured_outputs": false
        },
        "enabled": [],
        "enabled_count": 0,
        "initialize_capability_keys": [
          "tools"
        ]
      },
      "latency_ms": null,
      "status": "missing"
    },
    "connector_publishability_probe": {
      "details": {
        "blockers": [
          "transport_compliance",
          "server_card"
        ],
        "criteria": {
          "action_safety": true,
          "auth_flow": true,
          "connector_replay": true,
          "initialize": true,
          "protocol_version": true,
          "remote_transport": true,
          "request_association": true,
          "server_card": false,
          "session_resume": true,
          "step_up_auth": true,
          "tool_surface": true,
          "tools_list": true,
          "transport_compliance": false
        },
        "high_risk_tools": 0,
        "tool_count": 1,
        "transport": "streamable-http"
      },
      "latency_ms": null,
      "status": "warning"
    },
    "connector_replay_probe": {
      "details": {
        "reason": "no_historical_snapshot"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "determinism_probe": {
      "details": {
        "attempts": 2,
        "baseline_signature": "2558308c081e418246d13d127483a0a033e20815fbfd0bb09c4e1544bead07ba",
        "errors": [],
        "matches": 2,
        "stable_ratio": 1.0,
        "successful": 2
      },
      "latency_ms": 16.04,
      "status": "ok"
    },
    "initialize": {
      "details": {
        "headers": {
          "content-type": "application/json; charset=utf-8"
        },
        "http_status": 200,
        "payload": {
          "id": 1,
          "jsonrpc": "2.0",
          "result": {
            "capabilities": {
              "tools": {}
            },
            "instructions": "Maryland property-assessment fairness checks from the state's own roll (SDAT, 2.4M parcels). Compares an address against genuinely similar homes in the same triennial reassessment group and returns a fairness verdict plus Maryland's appeal windows. Please relay the honesty notes verbatim: this is a fairness snapshot of the public record, never an appraisal, and the official SDAT record is authoritative.",
            "protocolVersion": "2025-03-26",
            "serverInfo": {
              "name": "overassessed",
              "version": "0.1"
            }
          }
        },
        "url": "https://overassessed.agentlookups.ai/mcp"
      },
      "latency_ms": 47.44,
      "status": "ok"
    },
    "interactive_flow_probe": {
      "details": {
        "oauth_supported": false,
        "prompt_available": false,
        "risk_hits": [],
        "safe_hits": []
      },
      "latency_ms": null,
      "status": "missing"
    },
    "oauth_authorization_server": {
      "details": {
        "reason": "no_authorization_server"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "oauth_protected_resource": {
      "details": {
        "error": "Client error '404 Not Found' for url 'https://overassessed.agentlookups.ai/.well-known/oauth-protected-resource'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
        "url": "https://overassessed.agentlookups.ai/.well-known/oauth-protected-resource"
      },
      "latency_ms": 61.69,
      "status": "error"
    },
    "official_registry_probe": {
      "details": {
        "direct_match": true,
        "official_peer_count": 1,
        "registry_identifier": "ai.agentlookups/overassessed",
        "registry_source": "official_registry"
      },
      "latency_ms": null,
      "status": "ok"
    },
    "openid_configuration": {
      "details": {
        "reason": "no_authorization_server"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "probe_noise_resilience": {
      "details": {
        "headers": {
          "content-type": "text/plain; charset=utf-8"
        },
        "http_status": 200,
        "url": "https://overassessed.agentlookups.ai/robots.txt"
      },
      "latency_ms": 15.91,
      "status": "ok"
    },
    "prompt_get": {
      "details": {
        "reason": "not_advertised"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "prompts_list": {
      "details": {
        "headers": {
          "content-type": "application/json; charset=utf-8"
        },
        "http_status": 200,
        "payload": {
          "error": {
            "code": -32601,
            "message": "method not found: prompts/list"
          },
          "id": 3,
          "jsonrpc": "2.0"
        },
        "reason": "not_supported",
        "url": "https://overassessed.agentlookups.ai/mcp"
      },
      "latency_ms": 15.2,
      "status": "missing"
    },
    "protocol_version_probe": {
      "details": {
        "claimed_version": "2025-03-26",
        "lag_days": 244,
        "latest_known_version": "2025-11-25",
        "releases_behind": 2,
        "validator_protocol_version": "2025-03-26"
      },
      "latency_ms": null,
      "status": "warning"
    },
    "provenance_divergence_probe": {
      "details": {
        "direct_official_match": true,
        "drift_fields": [],
        "metadata_document_count": 1,
        "registry_homepage": null,
        "registry_repository": null,
        "registry_title": null,
        "registry_version": null,
        "server_card_homepage": null,
        "server_card_repository": null,
        "server_card_title": null,
        "server_card_version": null
      },
      "latency_ms": null,
      "status": "ok"
    },
    "request_association_probe": {
      "details": {
        "reason": "no_request_association_capabilities_advertised"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "resource_read": {
      "details": {
        "reason": "not_advertised"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "resources_list": {
      "details": {
        "headers": {
          "content-type": "application/json; charset=utf-8"
        },
        "http_status": 200,
        "payload": {
          "error": {
            "code": -32601,
            "message": "method not found: resources/list"
          },
          "id": 5,
          "jsonrpc": "2.0"
        },
        "reason": "not_supported",
        "url": "https://overassessed.agentlookups.ai/mcp"
      },
      "latency_ms": 16.56,
      "status": "missing"
    },
    "server_card": {
      "details": {
        "error": "Client error '404 Not Found' for url 'https://overassessed.agentlookups.ai/.well-known/mcp/server-card.json'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
        "url": "https://overassessed.agentlookups.ai/.well-known/mcp/server-card.json"
      },
      "latency_ms": 64.62,
      "status": "error"
    },
    "session_resume_probe": {
      "details": {
        "protocol_version": "2025-03-26",
        "reason": "no_session_id",
        "resume_expected": true,
        "transport": "streamable-http"
      },
      "latency_ms": null,
      "status": "warning"
    },
    "step_up_auth_probe": {
      "details": {
        "auth_required_checks": [],
        "broad_scopes": [],
        "challenge_headers": [],
        "minimal_scope_documented": false,
        "oauth_present": false,
        "scope_specificity_ratio": 0.0,
        "step_up_signals": [],
        "supported_scopes": []
      },
      "latency_ms": null,
      "status": "missing"
    },
    "tool_snapshot_probe": {
      "details": {
        "current_tool_count": 1,
        "reason": "no_historical_snapshot"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "tools_list": {
      "details": {
        "headers": {
          "content-type": "application/json; charset=utf-8"
        },
        "http_status": 200,
        "payload": {
          "id": 2,
          "jsonrpc": "2.0",
          "result": {
            "tools": [
              {
                "description": "Fairness check for a Maryland property assessment: where the address sits among genuinely similar homes (same reassessment group, similar size/lot/age, same zip), the group's median sales ratio, verdict branch (fair/review/elevated/insufficient), and Maryland's appeal windows with official filing links. If several parcels share the address, returns multiple_matches with account ids; re-call with acct.",
                "inputSchema": {
                  "properties": {
                    "acct": {
                      "description": "SDAT account id from a prior multiple_matches result (wins over address)",
                      "type": "string"
                    },
                    "address": {
                      "description": "Street address as the roll writes it, e.g. 1 STATE CIR (no unit numbers, no city)",
                      "type": "string"
                    },
                    "zip": {
                      "description": "5-digit zip (recommended; addresses repeat across Maryland)",
                      "type": "string"
                    }
                  },
                  "type": "object"
                },
                "name": "check_assessment"
              }
            ]
          }
        },
        "url": "https://overassessed.agentlookups.ai/mcp"
      },
      "latency_ms": 15.74,
      "status": "ok"
    },
    "transport_compliance_probe": {
      "details": {
        "bad_protocol_error": null,
        "bad_protocol_headers": {
          "content-type": "application/json; charset=utf-8"
        },
        "bad_protocol_payload": {
          "id": 410,
          "jsonrpc": "2.0",
          "result": {
            "tools": [
              {
                "description": "Fairness check for a Maryland property assessment: where the address sits among genuinely similar homes (same reassessment group, similar size/lot/age, same zip), the group's median sales ratio, verdict branch (fair/review/elevated/insufficient), and Maryland's appeal windows with official filing links. If several parcels share the address, returns multiple_matches with account ids; re-call with acct.",
                "inputSchema": {
                  "properties": {
                    "acct": {
                      "description": "SDAT account id from a prior multiple_matches result (wins over address)",
                      "type": "string"
                    },
                    "address": {
                      "description": "Street address as the roll writes it, e.g. 1 STATE CIR (no unit numbers, no city)",
                      "type": "string"
                    },
                    "zip": {
                      "description": "5-digit zip (recommended; addresses repeat across Maryland)",
                      "type": "string"
                    }
                  },
                  "type": "object"
                },
                "name": "check_assessment"
              }
            ]
          }
        },
        "bad_protocol_status_code": 200,
        "delete_error": null,
        "delete_status_code": null,
        "expired_session_error": null,
        "expired_session_status_code": null,
        "issues": [
          "missing_session_id",
          "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": 15.28,
      "status": "error"
    },
    "utility_coverage_probe": {
      "details": {
        "completions": {
          "advertised": false,
          "live_probe": "not_executed",
          "sample_target": null
        },
        "initialize_capability_keys": [
          "tools"
        ],
        "pagination": {
          "metadata_signal": false,
          "next_cursor_methods": [],
          "supported": false
        },
        "tasks": {
          "advertised": false,
          "http_status": 200,
          "probe_status": "missing"
        }
      },
      "latency_ms": 15.77,
      "status": "missing"
    }
  },
  "failures": {
    "oauth_authorization_server": {
      "reason": "no_authorization_server"
    },
    "oauth_protected_resource": {
      "error": "Client error '404 Not Found' for url 'https://overassessed.agentlookups.ai/.well-known/oauth-protected-resource'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
      "url": "https://overassessed.agentlookups.ai/.well-known/oauth-protected-resource"
    },
    "openid_configuration": {
      "reason": "no_authorization_server"
    },
    "server_card": {
      "error": "Client error '404 Not Found' for url 'https://overassessed.agentlookups.ai/.well-known/mcp/server-card.json'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
      "url": "https://overassessed.agentlookups.ai/.well-known/mcp/server-card.json"
    },
    "transport_compliance_probe": {
      "bad_protocol_error": null,
      "bad_protocol_headers": {
        "content-type": "application/json; charset=utf-8"
      },
      "bad_protocol_payload": {
        "id": 410,
        "jsonrpc": "2.0",
        "result": {
          "tools": [
            {
              "description": "Fairness check for a Maryland property assessment: where the address sits among genuinely similar homes (same reassessment group, similar size/lot/age, same zip), the group's median sales ratio, verdict branch (fair/review/elevated/insufficient), and Maryland's appeal windows with official filing links. If several parcels share the address, returns multiple_matches with account ids; re-call with acct.",
              "inputSchema": {
                "properties": {
                  "acct": {
                    "description": "SDAT account id from a prior multiple_matches result (wins over address)",
                    "type": "string"
                  },
                  "address": {
                    "description": "Street address as the roll writes it, e.g. 1 STATE CIR (no unit numbers, no city)",
                    "type": "string"
                  },
                  "zip": {
                    "description": "5-digit zip (recommended; addresses repeat across Maryland)",
                    "type": "string"
                  }
                },
                "type": "object"
              },
              "name": "check_assessment"
            }
          ]
        }
      },
      "bad_protocol_status_code": 200,
      "delete_error": null,
      "delete_status_code": null,
      "expired_session_error": null,
      "expired_session_status_code": null,
      "issues": [
        "missing_session_id",
        "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://overassessed.agentlookups.ai/mcp",
  "server_card_payload": null,
  "server_identifier": "ai.agentlookups/overassessed"
}
Known versions
  • 1.0.0
Validation history

Trend history appears after at least two validation runs. This avoids presenting a one-point validation as a trend.

Validation timeline
ValidatedSummaryScoreProtocolAuth modeToolsHigh-risk toolsChanges
Aug 05, 2026 02:00:09 AM UTC Healthy 69.5 2025-03-26 public 1 0 none
Recent validation runs
Recent validation runs for this MCP server
StartedStatusSummaryLatencyChecks
Aug 05, 2026 02:00:09 AM UTC Completed Healthy 306.4 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
Public server reputation
Validation success 7d
1.0
Validation success 30d
1.0
Mean time to recover
n/a
Breaking diffs 30d
0
Registry drift frequency 30d
0
Snapshot changes 30d
0
Incident & change feed
TimestampEventDetails
Aug 05, 2026 02:00:09 AM UTC Latest validation: healthy Score 69.5 with status healthy.
Capabilities
Use-case taxonomy
development automation
Benchmark tasks
Benchmark taskStatusEvidence
Discover tools Passes
  • initialize • OK
  • tools_list • OK
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 Passes
  • action_safety_probe • OK
Utility coverage
Probe status
Missing
Completions
not detected
Completion probe target: none
Pagination
not detected
No nextCursor evidence.
Tasks
Missing
Advertised: no
Transport compliance drilldown
Probe status
Error
Transport
streamable-http
Session header
no
Protocol header
no
Bad protocol response
200
DELETE teardown
n/a
Expired session retry
n/a
Last-Event-ID visible
no

Issues: missing_session_id, 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
Connector replay
Status
Missing
Backward compatible
✕
Would break after refresh
✕
Added tools
none
Removed tools
none
Additive output changes
none
Required-argument replay breaks
ToolAdded required argsRemoved required args
No required-argument replay breaks detected.
Output-schema replay breaks
ToolRemoved propertiesAdded properties
No output-schema replay breaks detected.
Tool snapshot diff & changelog

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

Validation diff

Need at least two validation runs before diffing changes.

Registry & provenance divergence
Probe status
OK
Direct official match
yes
Drift fields
none
FieldRegistryLive server card
Titlen/an/a
Versionn/an/a
Homepagen/an/a
Active alerts

No active alerts for the current server state.

Aliases & registry graph
IdentifierSourceCanonicalScore
ai.agentlookups/overassessed official_registry yes 69.5
Alias consolidation
Canonical identifier
ai.agentlookups/overassessed
Duplicate aliases
0
Registry sources
official_registry
Remote URLs
Homepages
none
Source disagreements
FieldWhat differsObserved values
No source disagreements detected.

Fix it

Why this score?
Access & Protocol
31/44
Connectivity, auth, and transport expectations for common clients.
Interface Quality
31.4/56
How well the tool/resource interface communicates and behaves under automation.
Security Posture
27.5/36
How safely the exposed tool surface handles destructive actions, egress, execution, secrets, and risky inputs.
Reliability & Trust
18.75/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/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
3.4/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
2/4
Completeness of tool descriptions, parameter docs, examples, and schema shape.
Backward Compatibility
2/4
Stability score across tool schema/name drift relative to prior validations.
SLO Health
4/4
Availability, latency, and burst-failure profile across recent validation history.
Security Hygiene
2.5/4
HTTPS posture, endpoint hygiene, and response-surface hardening checks.
Task Success
4/4
Can an agent reliably initialize, enumerate tools, and execute core MCP flows?
Trust Confidence
1.8/4
Confidence-adjusted reliability score that penalizes low evidence volume.
Abuse/Noise Resilience
4/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
3/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
4/4
How cleanly a real client can connect, initialize, enumerate tools, and proceed through auth.
Session Semantics
4/4
Determinism and state behavior across repeated MCP calls, including sticky-session surprises.
Tool Surface Design
3/4
Naming clarity, schema ergonomics, and parameter complexity across the tool surface.
Result Shape Stability
2/4
Stability of declared output schemas across validations, with penalties for drift or missing shapes.
OAuth Interop
3/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
3/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
4/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
1/4
Signals support for completions, pagination, and task-oriented utility surfaces that larger clients increasingly expect.
Advanced Capability Coverage
0/4
Coverage of newer MCP surfaces like roots, sampling, elicitation, structured output, and related metadata.
Connector Publishability
3/4
How ready the server looks for client catalogs and managed connector programs.
Tool Snapshot Churn
3/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
3/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
4/4
Clarity of docs, auth disclosure, support links, and other trust signals visible to integrators.
Tool Capability Clarity
4/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
3/4
Penalizes risky freeform string inputs when schemas do not constrain URLs, code, paths, queries, or templates.
Tool Namespace Clarity
4/4
Measures naming uniqueness and ambiguity across the tool namespace to reduce collision and confusion risk.
Actionable remediation
SeverityRemediationWhy it mattersRecommended action
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 Publish a complete server card Missing or incomplete server-card metadata weakens discovery, documentation, and trust signals. Serve /.well-known/mcp/server-card.json and include tools, prompts/resources, homepage, and support links.
Playbook
  • Publish `/.well-known/mcp/server-card.json`.
  • Include homepage, repository, support, tools, prompts/resources, and auth metadata.
  • Revalidate the server after publishing the card.
High Stop asking users to paste secrets directly Public MCP servers should prefer OAuth or browser-based auth guidance over in-band secret collection.
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 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.
Medium Support resumable HTTP sessions cleanly Modern MCP clients increasingly expect resumable session behavior on streamable HTTP transports. Persist session state keyed by Mcp-Session-Id and honor Last-Event-ID on GET reconnects so clients can resume a dropped Streamable HTTP session.
Playbook
  • Persist session state keyed by `Mcp-Session-Id` so a client can reconnect after a dropped connection.
  • Honor `Last-Event-ID` on GET reconnects to replay missed SSE events instead of erroring.
  • Revalidate and confirm `session_resume_probe` no longer returns `warning`.
Low Expose modern utility surfaces like completions, pagination, or tasks Utility coverage improves interoperability with larger clients and long-lived agent workflows. Expose completions, pagination, and task metadata where supported so larger clients can plan and resume work safely.
Playbook
  • Advertise `completions`, pagination cursors, and `tasks` only when they are actually supported.
  • Return `nextCursor` on large list operations when pagination is available.
  • Document task support and whether it requires step-up auth.
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
ComponentCurrentPoints missing
Transport Compliance 0/4 -4.0
Recovery Semantics 0/4 -4.0
Advanced Capability Coverage 0/4 -4.0
Utility Coverage 1/4 -3.0
Trust Confidence 1.8/4 -2.2
Spec Recency 2/4 -2.0
Schema Completeness 2/4 -2.0
Result Shape Stability 2/4 -2.0
Resource Contract 2/4 -2.0
Registry Consistency 2/4 -2.0
Rate Limit Semantics 2/4 -2.0
Prompt Contract 2/4 -2.0
Compatibility profiles
OpenAI Connectors
66.7
partial
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.; Transport compliance should be in good shape.
Connector URL: https://overassessed.agentlookups.ai/mcp
# No OAuth metadata detected.
# Server: ai.agentlookups/overassessed
Claude Desktop
83.3
compatible
Transport behavior should match Claude-compatible HTTP expectations.
{
  "mcpServers": {
    "overassessed": {
      "command": "npx",
      "args": ["mcp-remote", "https://overassessed.agentlookups.ai/mcp"]
    }
  }
}
Smithery
100.0
compatible
No major blockers detected.
smithery mcp add "https://overassessed.agentlookups.ai/mcp"
Generic Streamable HTTP
100.0
compatible
No major blockers detected.
curl -sS https://overassessed.agentlookups.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): 53.0 • 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 Write-Safe Claude Remote MCP Compatible 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
DeploymentStatusEndpointRelease
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://overassessed.agentlookups.ai/mcp
# No OAuth metadata detected.
# Server: ai.agentlookups/overassessed
Claude Desktop
{
  "mcpServers": {
    "overassessed": {
      "command": "npx",
      "args": ["mcp-remote", "https://overassessed.agentlookups.ai/mcp"]
    }
  }
}
Smithery
smithery mcp add "https://overassessed.agentlookups.ai/mcp"
Generic Http
curl -sS https://overassessed.agentlookups.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
check_assessment
Observed from the latest live validation against https://overassessed.agentlookups.ai/mcp. This is the target server surface, not Verify's own inspection tools.
Live capability counts
1 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.agentlookups/overassessed.
Direct machine links
JSON report • Compare this server • Verify MCP API