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

github-royalpinto007/casebook-mcp

royalpinto007/Casebook-MCP

A remote MCP server that turns AgentPostmortem, a public registry of documented AI-agent failures, into tools any agent can query. Ships with a companion investigator agent that drafts postmortems grounded in real precedents.

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

DECISION SUMMARY

Block For Production

Score

n/a

Percentile pending

Confidence

Low

Based on evidence completeness, recency, and validation density.

Evidence age

No validation evidence yet

Freshness: unknown. Snapshot trustsnap_e82c042b8a756d73.

Top risk drivers

Respond to server has never been validated
Raise Access & Protocol score
Raise Adoption & Market score

Recommended actions

Respond to server has never been validated
Tighten auth discovery, session behavior, and transport metadata until remote clients can connect without guesswork.
Increase external documentation and directory coverage so users can discover and evaluate the server.

Next action

revalidate, add safeguards, export policy

no validation evidence yet

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

Unknown

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

Missing

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: low (20.0)

Evidence provenance

Winner: live_validation

Supporting sources: live_validation, history, server_card

Disagreements: none

initialize • Missing
tools_list • Missing
transport_compliance_probe • Missing
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

Initialize must succeed or cleanly request auth.; tools/list must succeed.; A useful Claude integration needs at least one exposed tool.

Confidence: low (20.0)

Evidence provenance

Winner: live_validation

Supporting sources: live_validation, history, server_card

Disagreements: none

initialize • Missing
tools_list • Missing
transport_compliance_probe • Missing

Write-action publishing

Publishing blocked

Blocked until safeguards and confirmation semantics are verified for write, exec, or destructive tools.

Confidence: low (20.0)

Evidence provenance

Winner: live_validation

Supporting sources: live_validation, history

Disagreements: none

action_safety_probe • Missing

Snapshot churn risk

Low

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

Confidence: low (20.0)

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.
Initialize must be reachable.
tools/list must succeed.
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

Initialize must succeed or cleanly request auth.
tools/list must succeed.
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

Blocked

Remediation checklist

Add a clearer auth boundary around risky write actions.
Add confirmation or dry-run semantics for risky actions.

Verdict traces

Production verdict

Metadata only

No live validation evidence exists yet for this entry.

Confidence: low (20.0)

Winning source: metadata

Triggering alerts

never_validated • high • Server has never been validated

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 blocked	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.; Initialize must be reachable.; tools/list must succeed.; 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

Initialize must succeed or cleanly request auth.; tools/list must succeed.; 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

Initialize must succeed or cleanly request auth.; tools/list must succeed.; A useful Claude integration needs at least one exposed tool.

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

Recommended for

Metadata-first exploration only

Evidence confidence is still low, so verify the server manually before depending on it.

Evidence

Current trust snapshot

Snapshot ID

trustsnap_e82c042b8a756d73

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

Snapshot generated

Aug 05, 2026 05:35:14 PM UTC

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

Last validated

n/a

Age: n/ah • evidence age tier: Never validated • display score: suppressed

Canonical machine links

Compare index

/compare.json

Compare API

/v1/compare?server=github-royalpinto007%2Fcasebook-mcp

Trust summary

/v1/servers/github-royalpinto007/casebook-mcp/trust-summary

Report JSON

/v1/servers/github-royalpinto007/casebook-mcp/report

Policy export

/v1/servers/github-royalpinto007/casebook-mcp/policy

Badge metadata

/v1/servers/github-royalpinto007/casebook-mcp/badge

Ledger evidence

/v1/servers/github-royalpinto007/casebook-mcp/ledger

Human compare URL

/compare?server=github-royalpinto007%2Fcasebook-mcp

Evidence confidence

Confidence score

20.0

No live validation run exists yet; confidence is mostly metadata-derived.

Live checks captured

More direct checks increase trust in the current verdict.

Validation age

n/a

Lower age means fresher evidence.

Latest validation evidence

No validation run available yet.

Raw evidence view

Show raw JSON evidence

{
  "checks": {},
  "failures": {},
  "remote_url": "https://mcp.agentpostmortem.com",
  "server_card_payload": null,
  "server_identifier": "github-royalpinto007/casebook-mcp"
}

Known versions

No versions recorded.

Validation history

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

Validation timeline

No validation timeline is available yet.

Recent validation runs

Recent validation runs for this MCP server
Started	Status	Summary	Latency	Checks
No validation runs yet.

Public server reputation

Validation success 7d

n/a

Validation success 30d

n/a

Mean time to recover

n/a

Breaking diffs 30d

Registry drift frequency 30d

Snapshot changes 30d

Incident & change feed

No incidents or changes recorded yet.

Capabilities

OAuth: ✕
DCR/CIMD: ✕
Prompts: ✕
Homepage: https://mcp.agentpostmortem.com
Docs: https://mcp.agentpostmortem.com
Support: https://github.com/royalpinto007/Casebook-MCP
Icon: https://avatars.githubusercontent.com/u/97520428?v=4
Remote endpoint: https://mcp.agentpostmortem.com
Server card: none

Use-case taxonomy

development database productivity automation

Benchmark tasks

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

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

Missing

Transport

unknown

Session header

Protocol header

Bad protocol response

n/a

DELETE teardown

n/a

Expired session retry

n/a

Last-Event-ID visible

Issues: none

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

Need at least two validation runs before diffing changes.

Registry & provenance divergence

Probe status

Missing

Direct official match

Drift fields

none

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

Active alerts

Server has never been validated (high)
No live validation evidence exists yet for this entry.

Aliases & registry graph

Identifier	Source	Canonical	Score
`github-royalpinto007/casebook-mcp`	github_topic_registry	yes	n/a
`royalpinto007/casebook-mcp`	glama_registry	no	8.4

Alias consolidation

Canonical identifier

github-royalpinto007/casebook-mcp

Duplicate aliases

Registry sources

github_topic_registry glama_registry

Remote URLs

https://glama.ai/mcp/servers/jtd0vdcmr4

https://mcp.agentpostmortem.com

Homepages

https://glama.ai/mcp/servers/jtd0vdcmr4

https://mcp.agentpostmortem.com

Source disagreements

Field	What differs	Observed values
Registry source	Multiple registries or registry sync paths claim this same canonical server.	github_topic_registry glama_registry
Remote URL	Aliases currently point at different MCP endpoints, which can indicate mirrors, stale registry data, or a real endpoint split.	https://glama.ai/mcp/servers/jtd0vdcmr4 https://mcp.agentpostmortem.com
Homepage	Registry entries disagree on the primary homepage for this server.	https://glama.ai/mcp/servers/jtd0vdcmr4 https://mcp.agentpostmortem.com
Registry identifier	Different registry-specific identifiers resolve to the same canonical server record here.	github_topic_registry:royalpinto007/Casebook-MCP glama_registry:jtd0vdcmr4

Fix it

Why this score?

Access & Protocol

0/44

Connectivity, auth, and transport expectations for common clients.

Interface Quality

0/56

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

Security Posture

0/36

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

Reliability & Trust

0/24

Operational stability, consistency, and trustworthiness over time.

Discovery & Governance

0/28

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

Adoption & Market

0/8

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

Algorithmic score breakdown

No score components recorded yet.

Actionable remediation

Severity	Remediation	Why it matters	Recommended action
High	Respond to server has never been validated	No live validation evidence exists yet for this entry.
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 Adoption & Market score	Adoption clues and public evidence that the server is intended for external use.	Increase external documentation and directory coverage so users can discover and evaluate the server.
Medium	Raise Discovery & Governance score	How well the server is documented, listed, and governed in public registries.	Fill out homepage, docs, support, license, and registry metadata so directories stay aligned.
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.

Point loss breakdown

No current score penalties are recorded.

Compatibility profiles

OpenAI Connectors

44.4

blocked

Connector URL: https://mcp.agentpostmortem.com
# No OAuth metadata detected.
# Server: github-royalpinto007/casebook-mcp

Claude Desktop

50.0

blocked

Initialize must succeed or cleanly request auth.; tools/list must succeed.; A useful Claude integration needs at least one exposed tool.

{
  "mcpServers": {
    "casebook-mcp": {
      "command": "npx",
      "args": ["mcp-remote", "https://mcp.agentpostmortem.com"]
    }
  }
}

Smithery

20.0

blocked

Tool discovery must succeed.; Initialize should work before execution.; Metadata quality should be serviceable.; Machine-readable failure semantics should be present.

smithery mcp add "https://mcp.agentpostmortem.com"

Generic Streamable HTTP

33.3

blocked

Initialize must succeed.; tools/list must succeed.; Transport behavior should match metadata.; Session behavior should be predictable.

curl -sS https://mcp.agentpostmortem.com -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

Never validated

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

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 never_validated

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://mcp.agentpostmortem.com
# No OAuth metadata detected.
# Server: github-royalpinto007/casebook-mcp

Claude Desktop

{
  "mcpServers": {
    "casebook-mcp": {
      "command": "npx",
      "args": ["mcp-remote", "https://mcp.agentpostmortem.com"]
    }
  }
}

Smithery

smithery mcp add "https://mcp.agentpostmortem.com"

Generic Http

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

Agent access & tool surface

Live server tools

No live tool surface captured yet.

Observed from the latest live validation against https://mcp.agentpostmortem.com. 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 github-royalpinto007/casebook-mcp.

Direct machine links

JSON report • Compare this server • Verify MCP API