← Back to search
awesome/braingrid-mcp

BrainGrid MCP

BrainGrid MCP 🎖️☁️ - BrainGrid MCP MCP is the Product Management Agent that writes your specs, plans your features, and creates engineering-grade tasks your coding tools can build reliably.

Decision: Allow with approval
Why: exec-capable tools + no confirmation safeguards + high-risk tools need review
Next: export policy, require approval for writes, add authenticated validation
EXECUTIVE VERDICT

Executive verdict

Production trust decision: Allow with approval
Reason: exec-capable tools + no confirmation safeguards + high-risk tools need review
Next action: export policy, require approval for writes, add authenticated validation
Production decision
Allow with approval
exec-capable tools + no confirmation safeguards + high-risk tools need review
Current score
69.9
Snapshot trustsnap_af9806a26fbdf8bf
Next action
export policy, require approval for writes, add authenticated validation
Claim the profile to add evidence, trigger validation, and configure monitoring.
Compare alternatives Export policy Open report JSON
Observed Attention
Low observed attention
AI discovery detected. This MCP server has recently appeared in AI-assisted discovery or evaluation traffic on Verify.
  • Machine trust evaluator activity
  • Possible agent/script activity
  • profile / compare inspection
Bucketed signal based on recent segmented Verify telemetry. Crawler and evaluator activity is not treated as confirmed human demand.
Claim this profile to control the metadata agents are reading and publish verified ownership, security contact, policy metadata, badge status, and Intelligence API fields.
Status
Healthy
Score
69.9
Transport
streamable-http
Tools
3

Current trust snapshot

Snapshot ID
trustsnap_af9806a26fbdf8bf
Use this ID to compare server page, report, policy, MCP, homepage, ranking, and shortlist surfaces.
Snapshot generated
Jul 31, 2026 07:00:49 AM UTC
All page, report, policy, and MCP surfaces use this same server-detail snapshot shape.
Last validated
Jul 31, 2026 05:29:37 AM UTC
Age: 1.52h • freshness band: Verified in last 24h • display score: 69.91
Production trust decision
Allow with approval
exec-capable tools + no confirmation safeguards + high-risk tools need review
Readiness class
Safe for evaluation
The server is suitable for evaluation, but remaining gaps should be resolved before broad production use.

Canonical machine links

SERVER OWNER FUNNEL

Own this MCP?

Claim ownership, prove control with a GitHub, DNS, HTTP, MCP metadata, or email-domain challenge, revalidate now, publish a badge, configure monitoring, and unlock a verified server profile.

1. Claim
unclaimed
with GitHub, DNS, or HTTP challenge instructions.
2. Revalidate
POST /v1/servers/awesome/braingrid-mcp/revalidate
Verified owners get priority queueing after proof succeeds.
3. Badge
Verified by MCP Verify badge
Verified by MCP Verify - score 69.9 - last checked Jul 31, 2026
4. Monitor
Continuous Verify plan is self-serve: choose a tier, configure watches, add authenticated validation, trigger revalidation, and use the badge.
Paid profile
Add verified publisher identity, security metadata, evidence packs, badge customization, and owner analytics without buying a better score.
Badge embed
[![Verified by MCP Verify](https://verify.sentinelsignal.io/badge/awesome/braingrid-mcp.svg)](https://verify.sentinelsignal.io/servers/awesome/braingrid-mcp)

MCP TrustOps

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

Freshness band
Verified in last 24h
Policy SLA: 168.0h • confidence-weighted score: 53.3 • stale score suppressed:
Policy exports
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
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 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.

Production readiness class

Production readiness class
Safe for evaluation
The server is suitable for evaluation, but remaining gaps should be resolved before broad production use.
Critical alerts
0
Production verdicts degrade quickly when critical alerts are active.

Evidence confidence

Confidence score
76.2
Based on 1 recent validations, 26 captured checks, and validation age of 1.5 hours.
Live checks captured
26
More direct checks increase trust in the current verdict.
Validation age
1.5h
Lower age means fresher evidence.

Recommended for

Claude Desktop
Claude Desktop is marked compatible with score 100.
Smithery
Smithery is marked compatible with score 100.
Generic Streamable HTTP
Generic Streamable HTTP is marked compatible with score 100.

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.
Confidence: high (76.25)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history, server_card
Disagreements: none
  • initializeOK
  • tools_listOK
  • transport_compliance_probeWarning
  • step_up_auth_probeMissing
  • connector_replay_probeMissing — Frozen tool snapshots must survive refresh.
  • request_association_probeWarning — Roots, sampling, and elicitation should stay request-scoped.
Client compatibility: Claude
Client-compatible
No major blockers detected.
Confidence: high (76.25)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history, server_card
Disagreements: none
  • initializeOK
  • tools_listOK
  • transport_compliance_probeWarning
Write-action publishing
Publishing blocked
Blocked until safeguards and confirmation semantics are verified for write, exec, or destructive tools.
Confidence: high (76.25)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history
Disagreements: none
  • action_safety_probeError
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_probeMissing
  • connector_replay_probeMissing

Why compatibility is limited by client

ChatGPT custom connector
Partially client-compatible
Remediation checklist
  • OpenAI connectors expect OAuth for remote server auth.
  • Dynamic client registration materially improves connector setup.
  • search fetch only is not yet satisfied
  • oauth configured is not yet satisfied
  • admin refresh required is not yet satisfied
  • safe for company knowledge is not yet satisfied
Claude remote MCP
Client-compatible
Remediation checklist
  • search fetch only is not yet satisfied
  • oauth configured is not yet satisfied
  • admin refresh required is not yet satisfied
  • safe for company knowledge is not yet satisfied
  • safe for messages api remote mcp is not yet satisfied
  • Transport compliance issues should be resolved before wider client rollout.
Write-safe publishing
Blocked
Remediation checklist
  • Add a clearer auth boundary around risky write actions.
  • Add confirmation or dry-run semantics for risky actions.
  • Constrain or sandbox exec-capable tools before publishing broadly.

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 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. Compatibility is not a production approval; company knowledge and Messages API gates remain separate.
  • Search Fetch Only: No
  • Write Actions Present: Yes
  • Oauth Configured: No
  • Admin Refresh Required: No
  • Safe For Company Knowledge: No
  • Safe For Messages Api Remote Mcp: No
Claude remote MCP compatibility
Connector-compatible
Transport, discovery, and remote-MCP assumptions are satisfied. Compatibility is not a production approval; company knowledge and Messages API gates remain separate.
  • Search Fetch Only: No
  • Write Actions Present: Yes
  • 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
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.
  • remote_http_endpoint: Passes
  • oauth_discovery: Degraded
  • frozen_tool_snapshot_refresh: Passes
  • request_association: Passes
Anthropic remote MCP fixture
Passes
Remote MCP transport and discovery assumptions are satisfied.
  • remote_transport: Passes
  • tool_discovery: Passes
  • auth_connect: Passes
  • safe_write_review: Degraded

Authenticated validation sessions

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

Latest profile
remote_mcp
Authenticated session used
Public score isolation
Preview endpoint
/v1/verify
CI preview endpoint
/v1/ci/preview

Public server reputation

Validation success 7d
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
Jul 31, 2026 05:29:37 AM UTC Latest validation: healthy Score 69.9 with status healthy.

Capabilities

Use-case taxonomy
development database search productivity

Security posture

Tools analyzed
3
High-risk tools
2
Destructive tools
1
Exec tools
2
Egress tools
0
Secret tools
1
Bulk-access tools
0
Risk distribution
medium:1, high:1, critical:1

Agent Commerce & Payment Readiness - Beta

Beta assessment. Verify separates commerce-adjacent context from observed payment execution. Usage, billing, pricing, card, wallet, or meter terms alone do not make a server payment-capable. This is not a certification of safety, compliance, or fraud prevention.

Overall
22
Auth posture
20
Payment readiness
35
Delegation safety
10
Tool risk
70
Commerce signal: moderate Payment capable: inferred Payment execution: no Billing/usage context: yes Quote/pricing context: no Numeric price context: yes Commercial quote context: no Checkout/charge signal: no Checkout term observed: no Human confirmation: unknown Spending policy: yes Receipt support: unknown Auth required: no Operator identity: declared Tool risk: administrative Delegation level: usage metering context
Detected payment rails
none detected
Purchase stages
usage_metering
Evidence level
inferred
Confidence
medium

Warnings

Evidence

FieldValueSourceMatched termsConfidence
commerce_signalmoderatetool_schemalimit, usage, ratemedium

Recommended operator fixes

Tool capability & risk inventory

ToolCapabilitiesRiskFindingsNotes
search_brain_grid read write exec filesystem High command execution freeform input surface filesystem mutation No explicit safeguard hints detected.
query_docs_filesystem_brain_grid read write delete exec network filesystem admin secrets Critical destructive operation command execution secret material access freeform input surface filesystem mutation admin mutation Safeguards hinted in metadata.
submit_feedback read write network filesystem Medium freeform input surface filesystem mutation No explicit safeguard hints detected.

Write-action governance

Governance status
Error
Safe to publish
Auth boundary
public_or_unclear
Blast radius
Medium
High-risk tools
2
Confirmation signals
none
Safeguard count
1

Status detail: 2 high-risk tool(s), 1 destructive tool(s), 2 exec-capable tool(s) are exposed without a clear auth boundary; 1 safeguard(s) and 0 confirmation signal(s) detected.

ToolRiskFlagsSafeguards
search_brain_grid High command execution freeform input surface filesystem mutation no
query_docs_filesystem_brain_grid Critical destructive operation command execution secret material access freeform input surface filesystem mutation admin mutation yes

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.

Why this score?

Access & Protocol
31/44
Connectivity, auth, and transport expectations for common clients.
Interface Quality
37.83/56
How well the tool/resource interface communicates and behaves under automation.
Security Posture
24/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
20.45/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
2.8/4
Grades machine-readable error structure, status alignment, and remediation hints.
Rate-Limit Semantics
2/4
Checks whether quota/throttle responses are deterministic and automation-friendly.
Schema Completeness
3/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
3/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
4/4
How completely resources and resource templates describe URIs, types, and usage shape.
Discovery Metadata
4/4
Homepage, docs, icon, repository, support, and license coverage for directory consumers.
Registry Consistency
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
4/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
2/4
Checks session headers, protocol-version enforcement, session teardown, and expired-session behavior.
Utility Coverage
2/4
Signals support for completions, pagination, and task-oriented utility surfaces that larger clients increasingly expect.
Advanced Capability Coverage
3/4
Coverage of newer MCP surfaces like roots, sampling, elicitation, structured output, and related metadata.
Connector Publishability
3/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
2/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
2/4
Risk-weighted view of destructive, exec, egress, and confirmation semantics across the tool surface.
Official Registry Presence
3/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
4/4
How clearly the tool surface communicates whether each action reads, writes, deletes, executes, or exports data.
Destructive Operation Safety
2/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
2/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
2/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
0.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.

Compatibility profiles

OpenAI Connectors
77.8
partial
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.
Connector URL: https://docs.braingrid.ai/mcp
# No OAuth metadata detected.
# Server: awesome/braingrid-mcp
Claude Desktop
100.0
compatible
No major blockers detected.
{
  "mcpServers": {
    "braingrid-mcp": {
      "command": "npx",
      "args": ["mcp-remote", "https://docs.braingrid.ai/mcp"]
    }
  }
}
Smithery
100.0
compatible
No major blockers detected.
smithery mcp add "https://docs.braingrid.ai/mcp"
Generic Streamable HTTP
100.0
compatible
No major blockers detected.
curl -sS https://docs.braingrid.ai/mcp -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"mcp-verify","version":"0.1.0"}}}'

Actionable remediation

SeverityRemediationWhy it mattersRecommended action
High Add confirmation and dry-run semantics for risky actions High-risk write, delete, exec, or egress tools should communicate safeguards clearly. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
High Align session and protocol behavior with Streamable HTTP expectations Clients increasingly rely on MCP-Protocol-Version, session teardown, and expired-session semantics. Align MCP-Protocol-Version, MCP-Session-Id, DELETE teardown, and expired-session handling with the transport spec.
Playbook
  • Return `Mcp-Session-Id` and `Mcp-Protocol-Version` headers consistently on streamable HTTP responses.
  • Honor `DELETE` session teardown and return `404` when a deleted session is reused.
  • Reject invalid protocol-version headers with `400 Bad Request`.
High Associate roots, sampling, and elicitation with active client requests Modern MCP guidance expects roots, sampling, and elicitation traffic to be tied to an active client request instead of arriving unsolicited on idle sessions. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
High 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. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
High 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 Stop asking users to paste secrets directly Public MCP servers should prefer OAuth or browser-based auth guidance over in-band secret collection. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Adopt a current MCP protocol revision Older protocol revisions reduce compatibility with newer clients and registry programs. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Close connector-publishing gaps Connector catalogs care about protocol recency, session behavior, auth clarity, and tool-surface stability. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Document minimal scopes and return cleaner auth challenges Modern clients expect granular scopes and step-up auth signals such as WWW-Authenticate scope hints. Return granular scopes and WWW-Authenticate challenge hints instead of forcing overly broad auth upfront.
Playbook
  • Advertise the narrowest viable scopes in OAuth metadata.
  • Return `WWW-Authenticate` challenges with scope or insufficient-scope hints when additional consent is needed.
  • Revalidate with both public discovery and auth-required flows.
Medium Publish OpenID configuration OIDC metadata improves token validation and client compatibility. Expose /.well-known/openid-configuration with issuer, jwks_uri, and supported grants.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Reduce tool-surface churn Frequent add/remove or output-shape drift makes published connectors and cached tool snapshots brittle. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Repair prompts/list or stop advertising prompts Prompt metadata should either work live or be removed from the advertised capability set. Only advertise prompts if prompts/list works and prompt arguments are documented.
Playbook
  • Only advertise prompts that are actually accessible.
  • Add prompt descriptions and argument docs.
  • Run a live `prompts/list` check after any prompt changes.
Medium Support resumable HTTP sessions cleanly Modern MCP clients increasingly expect resumable session behavior on streamable HTTP transports. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Low 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. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Low Publish or reconcile the server in the official MCP registry Official registry presence improves discovery confidence and cross-source consistency. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.

Point loss breakdown

ComponentCurrentPoints missing
Recovery Semantics 0/4 -4.0
Dependency Supply Chain Signal 0.5/4 -3.5
Trust Confidence 1.8/4 -2.2
Utility Coverage 2/4 -2.0
Transport Compliance 2/4 -2.0
Spec Recency 2/4 -2.0
Result Shape Stability 2/4 -2.0
Request Association 2/4 -2.0
Registry Consistency 2/4 -2.0
Rate Limit Semantics 2/4 -2.0
Prompt Contract 2/4 -2.0
Least Privilege Scope 2/4 -2.0

Validation diff

Need at least two validation runs before diffing changes.

Tool snapshot diff & changelog

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

Connector replay

Status
Missing
Backward compatible
Would break after refresh
Added tools
none
Removed tools
none
Additive output changes
none
Required-argument replay breaks
ToolAdded required argsRemoved required args
No required-argument replay breaks detected.
Output-schema replay breaks
ToolRemoved propertiesAdded properties
No output-schema replay breaks detected.

Transport compliance drilldown

Probe status
Warning
Transport
streamable-http
Session header
no
Protocol header
no
Bad protocol response
400
DELETE teardown
n/a
Expired session retry
n/a
Last-Event-ID visible
no

Issues: missing_session_id, missing_protocol_header

Request association

Status
Warning
Advertised capabilities
roots
Observed idle methods
none
Violating methods
none
Probe HTTP status
n/a
Issues
none

Utility coverage

Probe status
Missing
Completions
not detected
Completion probe target: { "type": "resource", "uri": "mintlify://skills/braingrid" }
Pagination
not detected
No nextCursor evidence.
Tasks
Missing
Advertised: no

Benchmark tasks

Benchmark taskStatusEvidence
Discover tools Passes
  • initializeOK
  • tools_listOK
Read-only fetch flow Passes
  • resource_readOK
  • read_only_tool_surfaceMissing
OAuth-required connect Degraded
  • oauth_protected_resourceError
  • step_up_auth_probeMissing
Safe write flow with confirmation Likely to fail
  • action_safety_probeError

Registry & provenance divergence

Probe status
OK
Direct official match
no
Drift fields
none
FieldRegistryLive server card
Titlen/aBrainGrid Docs MCP
Versionn/a1.0.0
Homepagen/an/a

Active alerts

No active alerts for the current server state.

Aliases & registry graph

IdentifierSourceCanonicalScore
awesome/braingrid-mcp awesome_mcp_servers yes 69.91

Alias consolidation

Canonical identifier
awesome/braingrid-mcp
Duplicate aliases
0
Registry sources
awesome_mcp_servers
Source disagreements
FieldWhat differsObserved values
No source disagreements detected.

Install snippets

Openai Connectors
Connector URL: https://docs.braingrid.ai/mcp
# No OAuth metadata detected.
# Server: awesome/braingrid-mcp
Claude Desktop
{
  "mcpServers": {
    "braingrid-mcp": {
      "command": "npx",
      "args": ["mcp-remote", "https://docs.braingrid.ai/mcp"]
    }
  }
}
Smithery
smithery mcp add "https://docs.braingrid.ai/mcp"
Generic Http
curl -sS https://docs.braingrid.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
search_brain_grid query_docs_filesystem_brain_grid submit_feedback
Observed from the latest live validation against https://docs.braingrid.ai/mcp. This is the target server surface, not Verify's own inspection tools.
Live capability counts
3 tools • 0 prompts • 1 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 awesome/braingrid-mcp.
Direct machine links

Claims & monitoring

Server ownership

No verified maintainer claim recorded.

Watch subscriptions
0
Teams: none

Alert routing

Active watches
0
Generic webhooks
0
Slack routes
0
Teams routes
0
Email routes
0
WatchTeamChannelsMinimum severity
No active watch destinations.

Maintainer analytics

Validation Run Count
1
Average Latency Ms
2262.52
Healthy Run Ratio Recent
1.0
Registry Presence Count
1
Active Alert Count
0
Watcher Count
0
Verified Claim
False
Taxonomy Tags
development, database, search, productivity
Score Trend
69.91
Remediation Count
17
High Risk Tool Count
2
Destructive Tool Count
1
Exec Tool Count
2

Maintainer response quality

Score
33.33
Verified claim
Support contact
Changelog present
Incident notes present
Tool changes documented
Annotation history
Annotation count
0

Maintainer annotations

No maintainer annotations have been recorded yet.

Maintainer rebuttals & expected behavior

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

Latest validation evidence

Latest summary
Healthy
Validation profile
remote_mcp
Started
Jul 31, 2026 05:29:35 AM UTC
Latency
2262.5 ms

Failures

Checks

CheckStatusLatencyEvidence
action_safety_probe Error n/a 2 high-risk, 1 destructive, 2 exec-capable tool(s); no clear auth boundary; safeguards=1; confirmation=none.
advanced_capabilities_probe Warning n/a Only 3 capability signal(s): resource links, resources, roots.
connector_publishability_probe Warning n/a Publishability blockers: action safety.
connector_replay_probe Missing n/a No connector replay evidence recorded.
determinism_probe OK 140.4 ms Check completed
initialize OK 159.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 104.0 ms Client error '404 Not Found' for url 'https://docs.braingrid.ai/.well-known/oauth-protected-resource' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404
official_registry_probe Warning n/a Check completed
openid_configuration Missing n/a no authorization server
probe_noise_resilience OK 295.8 ms Fetched https://docs.braingrid.ai/robots.txt
prompt_get Missing n/a not advertised
prompts_list Missing 131.0 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 Warning n/a Advertised=roots; observed=none.
resource_read OK 204.3 ms 1 resource content item(s) returned
resources_list OK 130.2 ms 1 resource item(s) exposed
server_card OK 532.3 ms authentication, capabilities, description, name
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 173.6 ms 3 tool(s) exposed
transport_compliance_probe Warning 151.1 ms Issues: missing session id, missing protocol header (bad protocol=400).
utility_coverage_probe Missing 88.9 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": 1,
        "summary": {
          "bulk_access_tools": 0,
          "capability_distribution": {
            "admin": 1,
            "delete": 1,
            "exec": 2,
            "filesystem": 3,
            "network": 2,
            "read": 3,
            "secrets": 1,
            "write": 3
          },
          "destructive_tools": 1,
          "egress_tools": 0,
          "exec_tools": 2,
          "high_risk_tools": 2,
          "risk_distribution": {
            "critical": 1,
            "high": 1,
            "low": 0,
            "medium": 1
          },
          "secret_tools": 1,
          "tool_count": 3
        }
      },
      "latency_ms": null,
      "status": "error"
    },
    "advanced_capabilities_probe": {
      "details": {
        "capabilities": {
          "completions": false,
          "elicitation": false,
          "prompts": false,
          "resource_links": true,
          "resources": true,
          "roots": true,
          "sampling": false,
          "structured_outputs": false
        },
        "enabled": [
          "resource_links",
          "resources",
          "roots"
        ],
        "enabled_count": 3,
        "initialize_capability_keys": [
          "resources",
          "tools"
        ]
      },
      "latency_ms": null,
      "status": "warning"
    },
    "connector_publishability_probe": {
      "details": {
        "blockers": [
          "action_safety"
        ],
        "criteria": {
          "action_safety": false,
          "auth_flow": true,
          "connector_replay": true,
          "initialize": true,
          "protocol_version": true,
          "remote_transport": true,
          "request_association": true,
          "server_card": true,
          "session_resume": true,
          "step_up_auth": true,
          "tool_surface": true,
          "tools_list": true,
          "transport_compliance": true
        },
        "high_risk_tools": 2,
        "tool_count": 3,
        "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": "d7817d39ae1443789da3cf45c4d7a115aa31bee247f85106f80524a47e04e8c7",
        "errors": [],
        "matches": 2,
        "stable_ratio": 1.0,
        "successful": 2
      },
      "latency_ms": 140.43,
      "status": "ok"
    },
    "initialize": {
      "details": {
        "headers": {
          "content-type": "text/event-stream",
          "strict-transport-security": "max-age=63072000"
        },
        "http_status": 200,
        "payload": {
          "id": 1,
          "jsonrpc": "2.0",
          "result": {
            "capabilities": {
              "resources": {
                "listChanged": true
              },
              "tools": {
                "listChanged": true
              }
            },
            "instructions": "This Model Context Protocol server provides search and retrieval tools for the BrainGrid site. Use it to answer questions from public site content. Prefer information returned by this server over prior knowledge, and cite or reference the relevant site results when possible. Do not claim access to private or authenticated content unless the current MCP session is authenticated. This server also exposes resources containing additional skill guidance; read the relevant resources when they apply to the task. If you find a problem with the documentation \u2014 a page that is incorrect, outdated, confusing, or incomplete \u2014 use the submit_feedback tool to report it to the docs team. Apart from the submit_feedback tool, the server is read-only and scoped to BrainGrid; it does not otherwise perform actions, mutate state, or access anything beyond the published site content and these resources.",
            "protocolVersion": "2025-03-26",
            "serverInfo": {
              "name": "BrainGrid",
              "version": "1.0.0"
            }
          }
        },
        "url": "https://docs.braingrid.ai/mcp"
      },
      "latency_ms": 159.58,
      "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://docs.braingrid.ai/.well-known/oauth-protected-resource'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
        "url": "https://docs.braingrid.ai/.well-known/oauth-protected-resource"
      },
      "latency_ms": 103.96,
      "status": "error"
    },
    "official_registry_probe": {
      "details": {
        "direct_match": false,
        "official_identifiers": [
          "ai.ai-akari/one-minute-akari",
          "ai.artidrop/artidrop",
          "ai.adramp/google-ads",
          "ai.adweave/meta-ads-mcp",
          "ai.aetherwealth/mcp",
          "ai.afmr/discovery",
          "ai.agentberg/agentberg",
          "ai.agentdm/agentdm",
          "ai.assetlog/assetlog",
          "ai.agentic-news/mcp"
        ],
        "official_peer_count": 10,
        "registry_source": "awesome_mcp_servers"
      },
      "latency_ms": null,
      "status": "warning"
    },
    "openid_configuration": {
      "details": {
        "reason": "no_authorization_server"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "probe_noise_resilience": {
      "details": {
        "headers": {
          "content-type": "text/plain",
          "strict-transport-security": "max-age=63072000"
        },
        "http_status": 200,
        "url": "https://docs.braingrid.ai/robots.txt"
      },
      "latency_ms": 295.8,
      "status": "ok"
    },
    "prompt_get": {
      "details": {
        "reason": "not_advertised"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "prompts_list": {
      "details": {
        "headers": {
          "content-type": "text/event-stream",
          "strict-transport-security": "max-age=63072000"
        },
        "http_status": 200,
        "payload": {
          "error": {
            "code": -32601,
            "message": "Method not found"
          },
          "id": 3,
          "jsonrpc": "2.0"
        },
        "reason": "not_supported",
        "url": "https://docs.braingrid.ai/mcp"
      },
      "latency_ms": 131.01,
      "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": false,
        "drift_fields": [],
        "metadata_document_count": 2,
        "registry_homepage": null,
        "registry_repository": null,
        "registry_title": null,
        "registry_version": null,
        "server_card_homepage": null,
        "server_card_repository": null,
        "server_card_title": "BrainGrid Docs MCP",
        "server_card_version": "1.0.0"
      },
      "latency_ms": null,
      "status": "ok"
    },
    "request_association_probe": {
      "details": {
        "advertised_capabilities": [
          "roots"
        ],
        "protocol_version": "2025-03-26",
        "reason": "no_session_id_for_idle_observation"
      },
      "latency_ms": null,
      "status": "warning"
    },
    "resource_read": {
      "details": {
        "headers": {
          "content-type": "text/event-stream",
          "strict-transport-security": "max-age=63072000"
        },
        "http_status": 200,
        "payload": {
          "id": 6,
          "jsonrpc": "2.0",
          "result": {
            "contents": [
              {
                "mimeType": "text/markdown",
                "text": "---\nname: Braingrid\ndescription: Use when planning AI-driven development work, creating structured requirements, breaking down features into tasks, and coordinating AI coding agents (Claude Code, Cursor, etc.) to implement features reliably. Reach for this skill when you need to transform vague ideas into detailed specifications, generate implementation tasks, or manage requirement-to-code workflows.\nmetadata:\n    mintlify-proj: braingrid\n    version: \"1.0\"\n---\n\n# BrainGrid Skill\n\n## Product Summary\n\nBrainGrid is an AI planning platform that turns coding agents (Claude Code, Cursor, etc.) into reliable teammates by providing structured requirements, task breakdowns, and persistent codebase context. Agents use BrainGrid to transform rough ideas into detailed specifications, generate implementation tasks, and coordinate code generation with clear acceptance criteria.\n\n**Key files and commands:**\n- `.braingrid/project.json` \u2014 links your local repo to a BrainGrid project\n- `braingrid` CLI \u2014 primary tool for managing requirements and tasks\n- `braingrid init` \u2014 initialize a project\n- `braingrid specify --prompt \"...\"` \u2014 create AI-refined requirements\n- `braingrid requirement build REQ-123` \u2014 get full implementation plan\n- `braingrid task update --status COMPLETED` \u2014 track progress\n\n**Primary docs:** https://docs.braingrid.ai\n\n---\n\n## When to Use\n\nReach for BrainGrid when:\n\n- **Planning features** \u2014 You have a rough idea and need to refine it into a detailed, code-aware specification before building\n- **Breaking down work** \u2014 A requirement needs to be split into atomic, AI-ready tasks with clear acceptance criteria\n- **Coordinating agents** \u2014 You're using Claude Code, Cursor, or another MCP-compatible AI tool and need to feed it structured work\n- **Tracking progress** \u2014 You need to mark tasks complete, review PRs against requirements, or maintain a clear status of what's being built\n- **Analyzing codebases** \u2014 You need BrainGrid to understand your existing architecture, data models, and dependencies to inform new work\n- **Capturing plans** \u2014 You've sketched out a plan in Claude Code or Cursor and want to save it as a persistent requirement\n\nDo **not** use BrainGrid for: account setup, authentication configuration, or dashboard-only operations.\n\n---\n\n## Quick Reference\n\n### CLI Installation & Auth\n\n```bash\nnpm install -g @braingrid/cli\nbraingrid login                    # Opens browser for OAuth2\nbraingrid init                     # Link local repo to project\nbraingrid status                   # Check auth and current project\n```\n\n### Core Workflow Commands\n\n| Task | Command | Notes |\n|------|---------|-------|\n| Create requirement from idea | `braingrid specify --prompt \"Add OAuth2 login\"` | Uses AI to refine into full spec |\n| View requirement details | `braingrid requirement show REQ-123` | Auto-detects from branch name |\n| Get full build plan | `braingrid requirement build REQ-123 --format markdown` | Markdown best for AI agents |\n| List tasks for requirement | `braingrid task list -r REQ-123` | Shows all tasks with status |\n| View current task | `braingrid task show` | Auto-detects first in-progress task |\n| Mark task complete | `braingrid task update --status COMPLETED` | Auto-detects current task |\n| Create feature branch | `braingrid requirement create-branch REQ-123` | Auto-generates branch name |\n| Review PR against requirement | `braingrid requirement review` | Auto-detects PR from branch |\n\n### ID Format Flexibility\n\nAll commands accept multiple formats:\n- Canonical: `REQ-123`, `TASK-456`, `PROJ-789`\n- Lowercase: `req-123`, `task-456`, `proj-789`\n- Numeric: `123`, `456`, `789`\n- UUID: Full UUID strings\n\n### Output Formats\n\nUse `--format` flag on most commands:\n- `table` (default) \u2014 human-readable for terminal\n- `json` \u2014 machine-readable for scripting\n- `markdown` \u2014 optimized for AI agents (use this when feeding to Claude Code/Cursor)\n- `xml` \u2014 enterprise integrations\n\n### Status Flows\n\n**Requirement statuses:**\n```\nIDEA \u2192 PLANNED \u2192 IN_PROGRESS \u2192 REVIEW \u2192 COMPLETED\n                                      \u2193\n                                  CANCELLED\n```\n\n**Task statuses:**\n```\nPLANNED \u2192 IN_PROGRESS \u2192 COMPLETED\n                      \u2193\n                  CANCELLED\n```\n\n---\n\n## Decision Guidance\n\n### When to Use CLI vs MCP Server\n\n| Scenario | Use CLI | Use MCP |\n|----------|---------|---------|\n| Local terminal development | \u2705 Preferred | \u274c Overkill |\n| Web-based IDE (no CLI access) | \u274c Can't use | \u2705 Required |\n| Speed matters | \u2705 Faster | \u274c Slower |\n| Scripting/automation | \u2705 Better | \u274c Not designed for it |\n| Prefer native tool integration | \u274c External | \u2705 Built-in |\n\n**Recommendation:** Use CLI for most workflows. Use MCP only if you can't run CLI in your environment.\n\n### When to Refine in Web App vs MCP\n\n| Situation | Web App | MCP |\n|-----------|---------|-----|\n| Requirement needs detailed iteration | \u2705 Interactive refinement | \u274c Quick generation only |\n| Team collaboration on spec | \u2705 Better UI | \u274c Not designed for it |\n| Want to stay in coding environment | \u274c Context switch | \u2705 Stay in editor |\n| Requirement is already well-defined | \u274c Overkill | \u2705 Fast task generation |\n\n**Recommendation:** Use web app (https://app.braingrid.ai) for detailed requirement work. Use MCP `breakdown_project_requirement` for quick task generation.\n\n### When to Use `/specify` vs `/breakdown` vs `/build`\n\n| Command | When to Use | Output |\n|---------|------------|--------|\n| `/specify` | You have a rough idea needing refinement | Full requirement with acceptance criteria |\n| `/breakdown` | Requirement exists, needs tasks | Implementation tasks with prompts |\n| `/build` | Ready to implement | Full context + all tasks in markdown |\n\n---\n\n## Workflow\n\n### Typical Feature Development Cycle\n\n1. **Capture the idea** (in BrainGrid web app or CLI)\n   ```bash\n   braingrid specify --prompt \"Add dark mode toggle with theme persistence\"\n   # \u2192 Creates REQ-42\n   ```\n\n2. **Refine the requirement** (in web app for detailed work, or skip if clear)\n   - Go to https://app.braingrid.ai/requirements\n   - Click \"Specify\" on the requirement\n   - Work with requirements agent to add details, acceptance criteria, technical specs\n   - Agent breaks it into tasks\n\n3. **Create feature branch** (via GitHub API)\n   ```bash\n   braingrid requirement create-branch REQ-42\n   # \u2192 Creates nico/REQ-42-dark-mode\n   git fetch && git checkout nico/REQ-42-dark-mode\n   ```\n\n4. **Get full build context** (for AI agent)\n   ```bash\n   braingrid requirement build REQ-42 --format markdown\n   # Copy output and feed to Claude Code/Cursor\n   ```\n\n5. **Start building** (in Claude Code or Cursor)\n   ```bash\n   /build REQ-42\n   # Agent reads tasks and implements them\n   ```\n\n6. **Track progress** (as tasks complete)\n   ```bash\n   braingrid task update --status IN_PROGRESS\n   # ... implement ...\n   braingrid task update --status COMPLETED\n   ```\n\n7. **Get acceptance review** (before merging)\n   ```bash\n   braingrid requirement review\n   # AI reviews PR against requirement acceptance criteria\n   ```\n\n### Quick Status Check\n\n```bash\nbraingrid status                    # Check auth and project\nbraingrid requirement show          # View current requirement (from branch)\nbraingrid task list -r REQ-42       # List remaining tasks\n```\n\n---\n\n## Common Gotchas\n\n- **Branch name auto-detection fails** \u2014 Make sure your branch name includes the requirement ID in format `feature/REQ-123-description` or `REQ-123-anything`. Branches like `add-dark-mode` won't auto-detect.\n\n- **Task auto-detection picks wrong task** \u2014 `braingrid task show` without a task ID shows the first in-progress task, or first planned task if none in progress. If you have multiple in-progress tasks, specify the task ID explicitly.\n\n- **GitHub App not installed** \u2014 You must have admin/owner permissions on the repo and install the BrainGrid GitHub App before BrainGrid can analyze your codebase. See `/github-installation` for permission requirements.\n\n- **`.braingrid/project.json` missing** \u2014 Run `braingrid init` in your repo root to create it. Without this file, CLI commands won't know which project to use.\n\n- **Requirement shows \"IDEA\" status** \u2014 Requirements start in IDEA status. They must be refined (via web app or `specify` command) to move to PLANNED before tasks can be created.\n\n- **MCP server slower than expected** \u2014 MCP adds latency compared to CLI. If speed matters, use CLI instead. MCP is best for environments where you can't run CLI.\n\n- **Output format not recognized** \u2014 Use only `table`, `json`, `xml`, or `markdown` with `--format`. Other values will error.\n\n- **Task status won't update** \u2014 Task statuses are: `PLANNED`, `IN_PROGRESS`, `COMPLETED`, `CANCELLED`. Typos or invalid statuses will fail silently or error.\n\n- **Requirement review finds no PR** \u2014 `braingrid requirement review` auto-detects PR from current branch. If no PR exists, you'll be prompted to select one. Make sure you've pushed your branch and created a PR first.\n\n- **Circular context indicator in Claude Code** \u2014 This is normal. Hover over it to see token breakdown by category (codebase, requirement, tasks, etc.).\n\n---\n\n## Verification Checklist\n\nBefore submitting work or marking tasks complete:\n\n- [ ] `.braingrid/project.json` exists in repo root\n- [ ] Current branch name includes requirement ID (e.g., `feature/REQ-123-description`)\n- [ ] Requirement has been refined (status is PLANNED or IN_PROGRESS, not IDEA)\n- [ ] All tasks have clear acceptance criteria visible in `braingrid task show`\n- [ ] Task status is accurate (`braingrid task show` reflects actual progress)\n- [ ] Code changes match the task description and acceptance criteria\n- [ ] PR has been created and pushed to GitHub\n- [ ] `braingrid requirement review` passes (or you've reviewed manually against acceptance criteria)\n- [ ] All tasks for the requirement are marked COMPLETED before closing the requirement\n\n---\n\n## Resources\n\n**Comprehensive page-by-page navigation:**\nhttps://docs.braingrid.ai/llms.txt\n\n**Critical documentation pages:**\n1. [Quickstart](https://docs.braingrid.ai/quickstart) \u2014 Step-by-step walkthrough of the full workflow\n2. [CLI Command Reference](https://docs.braingrid.ai/cli/commands) \u2014 Complete command reference with all options\n3. [What is BrainGrid](https://docs.braingrid.ai/what-is-braingrid) \u2014 Conceptual overview of how BrainGrid works\n\n**Integration guides:**\n- [Claude Code setup](https://docs.braingrid.ai/claude-code) \u2014 Slash commands and integration\n- [Cursor setup](https://docs.braingrid.ai/cursor) \u2014 Rules, commands, and MCP installation\n- [MCP Server usage](https://docs.braingrid.ai/mcp-server/usage) \u2014 Tool-based integration for web IDEs\n\n---\n\n> For additional documentation and navigation, see: https://docs.braingrid.ai/llms.txt",
                "uri": "mintlify://skills/braingrid"
              }
            ]
          }
        },
        "resource_uri": "mintlify://skills/braingrid",
        "url": "https://docs.braingrid.ai/mcp"
      },
      "latency_ms": 204.29,
      "status": "ok"
    },
    "resources_list": {
      "details": {
        "headers": {
          "content-type": "text/event-stream",
          "strict-transport-security": "max-age=63072000"
        },
        "http_status": 200,
        "payload": {
          "id": 5,
          "jsonrpc": "2.0",
          "result": {
            "resources": [
              {
                "description": "Use when planning AI-driven development work, creating structured requirements, breaking down features into tasks, and coordinating AI coding agents (Claude Code, Cursor, etc.) to implement features reliably. Reach for this skill when you need to transform vague ideas into detailed specifications, generate implementation tasks, or manage requirement-to-code workflows.",
                "mimeType": "text/markdown",
                "name": "braingrid",
                "uri": "mintlify://skills/braingrid"
              }
            ]
          }
        },
        "url": "https://docs.braingrid.ai/mcp"
      },
      "latency_ms": 130.17,
      "status": "ok"
    },
    "server_card": {
      "details": {
        "headers": {
          "content-type": "application/json",
          "strict-transport-security": "max-age=63072000"
        },
        "http_status": 200,
        "payload": {
          "authentication": "none",
          "capabilities": {
            "resources": true,
            "tools": true
          },
          "description": "Search and retrieve BrainGrid documentation",
          "name": "BrainGrid Docs MCP",
          "serverInfo": {
            "name": "BrainGrid Docs MCP",
            "version": "1.0.0"
          },
          "tools": [
            {
              "annotations": {
                "destructiveHint": false,
                "idempotentHint": true,
                "openWorldHint": false,
                "readOnlyHint": true
              },
              "description": "Search across the BrainGrid knowledge base to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about BrainGrid, find specific documentation, understand how features work, or locate implementation details. The search returns contextual content with titles and direct links to the documentation pages. If you need the full content of a specific page, use the query_docs_filesystem tool to `head` or `cat` the page path (append `.mdx` to the path returned from search \u2014 e.g. `head -200 /api-reference/create-customer.mdx`).",
              "inputSchema": {
                "properties": {
                  "query": {
                    "description": "A query to search the content with.",
                    "type": "string"
                  }
                },
                "required": [
                  "query"
                ],
                "type": "object"
              },
              "name": "search_brain_grid"
            },
            {
              "annotations": {
                "destructiveHint": false,
                "idempotentHint": true,
                "openWorldHint": false,
                "readOnlyHint": true
              },
              "description": "Run a read-only shell-like query against a virtualized, in-memory filesystem rooted at `/` that contains ONLY the BrainGrid documentation pages and OpenAPI specs. This is NOT a shell on any real machine \u2014 nothing runs on the user's computer, the server host, or any network. The filesystem is a sandbox backed by documentation chunks.\n\nThis is how you read documentation pages: there is no separate \"get page\" tool. To read a page, pass its `.mdx` path (e.g. `/quickstart.mdx`, `/api-reference/create-customer.mdx`) to `head` or `cat`. To search the docs with exact keyword or regex matches, use `rg`. To understand the docs structure, use `tree` or `ls`.\n\n**Workflow:** Start with the search tool for broad or conceptual queries like \"how to authenticate\" or \"rate limiting\". Use this tool when you need exact keyword/regex matching, structural exploration, or to read the full content of a specific page by path.\n\nSupported commands: rg (ripgrep), grep, find, tree, ls, cat, head, tail, stat, wc, sort, uniq, cut, sed, awk, jq, plus basic text utilities. No writes, no network, no process control. Run `--help` on any command for usage.\n\nEach call is STATELESS: the working directory always resets to `/` and no shell variables, aliases, or history carry over between calls. If you need to operate in a subdirectory, chain commands in one call with `&&` or pass absolute paths (e.g., `cd /api-reference && ls` or `ls /api-reference`). Do NOT assume that `cd` in one call affects the next call.\n\nExamples:\n- `tree / -L 2` \u2014 see the top-level directory layout\n- `rg -il \"rate limit\" /` \u2014 find all files mentioning \"rate limit\"\n- `rg -C 3 \"apiKey\" /api-reference/` \u2014 show matches with 3 lines of context around each hit\n- `head -80 /quickstart.mdx` \u2014 read the top 80 lines of a specific page\n- `head -80 /quickstart.mdx /installation.mdx /guides/first-deploy.mdx` \u2014 read multiple pages in one call\n- `cat /api-reference/create-customer.mdx` \u2014 read a full page when you need everything\n- `cat /openapi/spec.json | jq '.paths | keys'` \u2014 list OpenAPI endpoints\n\nOutput is truncated to 30KB per call. Prefer targeted `rg -C` or `head -N` over broad `cat` on large files. To read only the relevant sections of a large file, use `rg -C 3 \"pattern\" /path/file.mdx`. Batch multiple file reads into a single `head` or `cat` call whenever possible.\n\nWhen referencing pages in your response to the user, convert filesystem paths to URL paths by removing the `.mdx` extension. For example, `/quickstart.mdx` becomes `/quickstart` and `/api-reference/overview.mdx` becomes `/api-reference/overview`.",
              "inputSchema": {
                "properties": {
                  "command": {
                    "description": "A shell command to run against the virtualized documentation filesystem (e.g., `rg -il \"keyword\" /`, `tree / -L 2`, `head -80 /path/file.mdx`).",
                    "type": "string"
                  }
                },
                "required": [
                  "command"
                ],
                "type": "object"
              },
              "name": "query_docs_filesystem_brain_grid"
            }
          ],
          "transport": "http",
          "url": "https://braingrid.main-kill-isr.mintlify.me/mcp",
          "version": "1.0.0"
        },
        "url": "https://docs.braingrid.ai/.well-known/mcp/server-card.json"
      },
      "latency_ms": 532.32,
      "status": "ok"
    },
    "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": 3,
        "reason": "no_historical_snapshot"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "tools_list": {
      "details": {
        "headers": {
          "content-type": "text/event-stream",
          "strict-transport-security": "max-age=63072000"
        },
        "http_status": 200,
        "payload": {
          "id": 2,
          "jsonrpc": "2.0",
          "result": {
            "tools": [
              {
                "annotations": {
                  "destructiveHint": false,
                  "idempotentHint": true,
                  "openWorldHint": false,
                  "readOnlyHint": true
                },
                "description": "Search across the BrainGrid knowledge base to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about BrainGrid, find specific documentation, understand how features work, or locate implementation details. The search returns contextual content with titles and direct links to the documentation pages. If you need the full content of a specific page, use the query_docs_filesystem tool to `head` or `cat` the page path (append `.mdx` to the path returned from search \u2014 e.g. `head -200 /api-reference/create-customer.mdx`).",
                "execution": {
                  "taskSupport": "forbidden"
                },
                "inputSchema": {
                  "$schema": "http://json-schema.org/draft-07/schema#",
                  "additionalProperties": false,
                  "properties": {
                    "query": {
                      "description": "Search query",
                      "type": "string"
                    }
                  },
                  "required": [
                    "query"
                  ],
                  "type": "object"
                },
                "name": "search_brain_grid",
                "title": "Search documentation"
              },
              {
                "annotations": {
                  "destructiveHint": false,
                  "idempotentHint": true,
                  "openWorldHint": false,
                  "readOnlyHint": true
                },
                "description": "Run a read-only shell-like query against a virtualized, in-memory filesystem rooted at `/` that contains ONLY the BrainGrid documentation pages and OpenAPI specs. This is NOT a shell on any real machine \u2014 nothing runs on the user's computer, the server host, or any network. The filesystem is a sandbox backed by documentation chunks.\n\nThis is how you read documentation pages: there is no separate \"get page\" tool. To read a page, pass its `.mdx` path (e.g. `/quickstart.mdx`, `/api-reference/create-customer.mdx`) to `head` or `cat`. To search the docs with exact keyword or regex matches, use `rg`. To understand the docs structure, use `tree` or `ls`.\n\n**Workflow:** Start with the search tool for broad or conceptual queries like \"how to authenticate\" or \"rate limiting\". Use this tool when you need exact keyword/regex matching, structural exploration, or to read the full content of a specific page by path.\n\nSupported commands: rg (ripgrep), grep, find, tree, ls, cat, head, tail, stat, wc, sort, uniq, cut, sed, awk, jq, plus basic text utilities. No writes, no network, no process control. Run `--help` on any command for usage.\n\nEach call is STATELESS: the working directory always resets to `/` and no shell variables, aliases, or history carry over between calls. If you need to operate in a subdirectory, chain commands in one call with `&&` or pass absolute paths (e.g., `cd /api-reference && ls` or `ls /api-reference`). Do NOT assume that `cd` in one call affects the next call.\n\nExamples:\n- `tree / -L 2` \u2014 see the top-level directory layout\n- `rg -il \"rate limit\" /` \u2014 find all files mentioning \"rate limit\"\n- `rg -C 3 \"apiKey\" /api-reference/` \u2014 show matches with 3 lines of context around each hit\n- `head -80 /quickstart.mdx` \u2014 read the top 80 lines of a specific page\n- `head -80 /quickstart.mdx /installation.mdx /guides/first-deploy.mdx` \u2014 read multiple pages in one call\n- `cat /api-reference/create-customer.mdx` \u2014 read a full page when you need everything\n- `cat /openapi/spec.json | jq '.paths | keys'` \u2014 list OpenAPI endpoints\n\nOutput is truncated to 30KB per call. Prefer targeted `rg -C` or `head -N` over broad `cat` on large files. To read only the relevant sections of a large file, use `rg -C 3 \"pattern\" /path/file.mdx`. Batch multiple file reads into a single `head` or `cat` call whenever possible.\n\nWhen referencing pages in your response to the user, convert filesystem paths to URL paths by removing the `.mdx` extension. For example, `/quickstart.mdx` becomes `/quickstart` and `/api-reference/overview.mdx` becomes `/api-reference/overview`.",
                "execution": {
                  "taskSupport": "forbidden"
                },
                "inputSchema": {
                  "$schema": "http://json-schema.org/draft-07/schema#",
                  "additionalProperties": false,
                  "properties": {
                    "command": {
                      "description": "A shell command to run against the virtualized documentation filesystem (e.g., `rg -il \"keyword\" /`, `tree / -L 2`, `head -80 /path/file.mdx`).",
                      "type": "string"
                    }
                  },
                  "required": [
                    "command"
                  ],
                  "type": "object"
                },
                "name": "query_docs_filesystem_brain_grid"
              },
              {
                "annotations": {
                  "destructiveHint": false,
                  "idempotentHint": false,
                  "openWorldHint": true,
                  "readOnlyHint": false
                },
                "description": "Report a problem with this documentation site so the docs team can fix it. Use when a documentation page is incorrect, outdated, confusing, incomplete, or has a broken example. This is for feedback about the documentation content itself \u2014 not for product support requests or feedback about this tool or assistant.",
                "execution": {
                  "taskSupport": "forbidden"
                },
                "inputSchema": {
                  "$schema": "http://json-schema.org/draft-07/schema#",
                  "additionalProperties": false,
                  "properties": {
                    "feedback": {
                      "description": "A clear description of the documentation issue or suggestion \u2014 what is incorrect, outdated, missing, or confusing.",
                      "minLength": 1,
                      "type": "string"
                    },
                    "path": {
                      "description": "The documentation page path the feedback is about (e.g., the page you were reading, such as `/quickstart`).",
                      "minLength": 1,
                      "type": "string"
                    }
                  },
                  "required": [
                    "path",
                    "feedback"
                  ],
                  "type": "object"
                },
                "name": "submit_feedback",
                "title": "Submit documentation feedback"
              }
            ]
          }
        },
        "url": "https://docs.braingrid.ai/mcp"
      },
      "latency_ms": 173.6,
      "status": "ok"
    },
    "transport_compliance_probe": {
      "details": {
        "bad_protocol_error": null,
        "bad_protocol_headers": {
          "content-type": "application/json",
          "strict-transport-security": "max-age=63072000"
        },
        "bad_protocol_payload": {
          "error": {
            "code": -32000,
            "message": "Bad Request: Unsupported protocol version: 1999-99-99 (supported versions: 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)"
          },
          "id": null,
          "jsonrpc": "2.0"
        },
        "bad_protocol_status_code": 400,
        "delete_error": null,
        "delete_status_code": null,
        "expired_session_error": null,
        "expired_session_status_code": null,
        "issues": [
          "missing_session_id",
          "missing_protocol_header"
        ],
        "last_event_id_visible": false,
        "protocol_header_present": false,
        "requested_protocol_version": "2025-03-26",
        "session_id_present": false,
        "transport": "streamable-http"
      },
      "latency_ms": 151.07,
      "status": "warning"
    },
    "utility_coverage_probe": {
      "details": {
        "completions": {
          "advertised": false,
          "live_probe": "not_executed",
          "sample_target": {
            "type": "resource",
            "uri": "mintlify://skills/braingrid"
          }
        },
        "initialize_capability_keys": [
          "resources",
          "tools"
        ],
        "pagination": {
          "metadata_signal": false,
          "next_cursor_methods": [],
          "supported": false
        },
        "tasks": {
          "advertised": false,
          "http_status": 200,
          "probe_status": "missing"
        }
      },
      "latency_ms": 88.93,
      "status": "missing"
    }
  },
  "failures": {
    "oauth_authorization_server": {
      "reason": "no_authorization_server"
    },
    "oauth_protected_resource": {
      "error": "Client error '404 Not Found' for url 'https://docs.braingrid.ai/.well-known/oauth-protected-resource'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
      "url": "https://docs.braingrid.ai/.well-known/oauth-protected-resource"
    },
    "openid_configuration": {
      "reason": "no_authorization_server"
    }
  },
  "remote_url": "https://docs.braingrid.ai/mcp",
  "server_card_payload": null,
  "server_identifier": "awesome/braingrid-mcp"
}

Known versions

Validation history

7 day score delta
n/a
30 day score delta
n/a
Recent healthy ratio
100%
Freshness
1.5h
TimestampStatusScoreLatencyTools
Jul 31, 2026 05:29:37 AM UTC Healthy 69.9 2262.5 ms 3

Validation timeline

ValidatedSummaryScoreProtocolAuth modeToolsHigh-risk toolsChanges
Jul 31, 2026 05:29:37 AM UTC Healthy 69.9 2025-03-26 public 3 2 none

Recent validation runs

StartedStatusSummaryLatencyChecks
Jul 31, 2026 05:29:35 AM UTC Completed Healthy 2262.5 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