← 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 + unauthenticated behavior not proven
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 + unauthenticated behavior not proven
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 + unauthenticated behavior not proven
Current score
72.9
Snapshot trustsnap_c7b118fac8072566
Next action
export policy, require approval for writes, add authenticated validation
Claim the profile to add evidence, trigger validation, and configure monitoring.
Claim this server Compare alternatives Export policy Open report JSON
Status
Degraded
Score
72.9
Transport
streamable-http
Tools
2

Current trust snapshot

Snapshot ID
trustsnap_c7b118fac8072566
Use this ID to compare server page, report, policy, MCP, homepage, ranking, and shortlist surfaces.
Snapshot generated
May 25, 2026 01:57:50 PM UTC
All page, report, policy, and MCP surfaces use this same server-detail snapshot shape.
Last validated
May 25, 2026 12:40:27 PM UTC
Age: 1.29h • freshness band: Verified in last 24h • display score: 72.94
Production trust decision
Allow with approval
exec-capable tools + no confirmation safeguards + high-risk tools need review + unauthenticated behavior not proven
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
Start owner claim 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 72.9 - last checked May 25, 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: 52.9 • 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 OAuth Verified 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
none
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
3
Production verdicts degrade quickly when critical alerts are active.

Evidence confidence

Confidence score
72.5
Based on 2 recent validations, 26 captured checks, and validation age of 1.3 hours.
Live checks captured
26
More direct checks increase trust in the current verdict.
Validation age
1.3h
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
Dynamic client registration materially improves connector setup.; OAuth interoperability should be strong.
Confidence: medium (72.5)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history, server_card
Disagreements: none
  • initializeOK
  • tools_listOK
  • transport_compliance_probeWarning
  • step_up_auth_probeWarning
  • connector_replay_probeOK — Frozen tool snapshots must survive refresh.
  • request_association_probeMissing — Roots, sampling, and elicitation should stay request-scoped.
Client compatibility: Claude
Client-compatible
No major blockers detected.
Confidence: medium (72.5)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history, server_card
Disagreements: none
  • initializeOK
  • tools_listOK
  • transport_compliance_probeWarning
Write-action publishing
Publishing allowed
Current write surface is bounded enough for cautious review with production policy controls.
Confidence: medium (72.5)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history
Disagreements: none
  • action_safety_probeWarning
Snapshot churn risk
Medium
The live tool surface changed between recent validations.
Confidence: medium (72.5)
Evidence provenance
Winner: history
Supporting sources: history, live_validation
Disagreements: none
  • tool_snapshot_probeOK
  • connector_replay_probeOK

Why compatibility is limited by client

ChatGPT custom connector
Partially client-compatible
Remediation checklist
  • Dynamic client registration materially improves connector setup.
  • OAuth interoperability should be strong.
  • search fetch only 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.
Claude remote MCP
Client-compatible
Remediation checklist
  • search fetch only 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
Ready
Remediation checklist
  • No explicit blockers recorded.

Verdict traces

Production verdict
Safe for evaluation
The server is suitable for evaluation, but remaining gaps should be resolved before broad production use.
Confidence: medium (72.5)
Winning source: live_validation
Triggering alerts
  • server_degraded • medium • Latest validation is degraded
  • tool_snapshot_changed • high • Tool snapshot changed
  • auth_mode_changed • high • Auth mode changed
  • write_action_surface_expanded • high • Write-action surface expanded
Client verdict trace table
VerdictStatusChecksWinning sourceConflicts
openai_connectors Partially client-compatible initialize, tools_list, transport_compliance_probe, step_up_auth_probe, connector_replay_probe, request_association_probe live_validation none
claude_desktop Client-compatible initialize, tools_list, transport_compliance_probe live_validation none
unsafe_for_write_actions Publishing allowed action_safety_probe live_validation none
snapshot_churn_risk Medium tool_snapshot_probe, connector_replay_probe history none

Publishability policy profiles

ChatGPT custom connector compatibility
Compatible with review
Dynamic client registration materially improves connector setup.; 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: Yes
  • Oauth Configured: Yes
  • Admin Refresh Required: Yes
  • 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: Yes
  • Admin Refresh Required: Yes
  • Safe For Company Knowledge: No
  • Safe For Messages Api Remote Mcp: No

Compatibility fixtures

ChatGPT custom connector fixture
Degraded
Dynamic client registration materially improves connector setup.; OAuth interoperability should be strong.
  • remote_http_endpoint: Passes
  • oauth_discovery: Passes
  • 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: Passes

Authenticated validation sessions

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

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

Public server reputation

Validation success 7d
0.0
Validation success 30d
0.0
Mean time to recover
n/a
Breaking diffs 30d
1
Registry drift frequency 30d
0
Snapshot changes 30d
1

Incident & change feed

TimestampEventDetails
May 25, 2026 12:40:27 PM UTC Latest validation: degraded Score 72.9 with status degraded.
May 25, 2026 12:40:27 PM UTC Score changed Score delta +4.5 versus the previous run.
May 25, 2026 12:40:27 PM UTC Tool snapshot changed Added 2, removed 0, and changed 0 tool contracts.
May 25, 2026 12:40:27 PM UTC Auth mode changed Auth mode moved from unknown to oauth_supported.

Capabilities

Use-case taxonomy
development database search productivity

Security posture

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

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.

Write-action governance

Governance status
Warning
Safe to publish
Auth boundary
oauth_or_auth_required
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); auth boundary is oauth or auth required with 1 safeguard(s) and 0 confirmation signal(s).

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
yes
Disabled-by-default candidates
query_docs_filesystem_brain_grid search_brain_grid
Manual review candidates
query_docs_filesystem_brain_grid search_brain_grid
New actions
ActionRiskFlags
query_docs_filesystem_brain_gridCriticaldestructive operation command execution secret material access freeform input surface filesystem mutation admin mutation
search_brain_gridHighcommand execution freeform input surface filesystem mutation
Changed actions
ActionChange typesRisk
No materially changed actions.

Why this score?

Access & Protocol
32.42/44
Connectivity, auth, and transport expectations for common clients.
Interface Quality
39.12/56
How well the tool/resource interface communicates and behaves under automation.
Security Posture
25/36
How safely the exposed tool surface handles destructive actions, egress, execution, secrets, and risky inputs.
Reliability & Trust
20.94/24
Operational stability, consistency, and trustworthiness over time.
Discovery & Governance
18.65/28
How well the server is documented, listed, and governed in public registries.
Adoption & Market
6.83/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.1/4
Grades machine-readable error structure, status alignment, and remediation hints.
Rate-Limit Semantics
2/4
Checks whether quota/throttle responses are deterministic and automation-friendly.
Schema Completeness
2/4
Completeness of tool descriptions, parameter docs, examples, and schema shape.
Backward Compatibility
4/4
Stability score across tool schema/name drift relative to prior validations.
SLO Health
3/4
Availability, latency, and burst-failure profile across recent validation history.
Security Hygiene
3/4
HTTPS posture, endpoint hygiene, and response-surface hardening checks.
Task Success
4/4
Can an agent reliably initialize, enumerate tools, and execute core MCP flows?
Trust Confidence
2.9/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
3/4
Stability of declared output schemas across validations, with penalties for drift or missing shapes.
OAuth Interop
2.4/4
Depth and client compatibility of OAuth/OIDC metadata beyond the minimal protected-resource check.
Recovery Semantics
0/4
Whether failures include actionable machine-readable next steps such as retry or upgrade guidance.
Maintenance Signal
3.1/4
Versioning, update recency, and historical validation cadence that indicate active stewardship.
Adoption Signal
3.8/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
4/4
Stability of the tool surface across recent validations, including add/remove and output-shape drift.
Connector Replay
4/4
Whether a previously published frozen connector snapshot would remain backward compatible after the latest tool refresh.
Request Association
3/4
Whether roots, sampling, and elicitation appear tied to active client requests instead of arriving unsolicited on idle sessions.
Interactive Flow Safety
3/4
Whether prompts and docs steer users toward safe auth flows instead of pasting secrets directly.
Action Safety
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
2/4
Clarity of docs, auth disclosure, support links, and other trust signals visible to integrators.
Tool Capability Clarity
4/4
How clearly the tool surface communicates whether each action reads, writes, deletes, executes, or exports data.
Destructive Operation Safety
3/4
Penalizes delete/revoke/destroy style tools unless auth and safeguards reduce blast radius.
Egress / SSRF Resilience
3/4
Assesses arbitrary URL fetch, crawl, webhook, and remote-request exposure on the tool surface.
Execution / Sandbox Safety
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
3/4
Rewards scoped auth metadata and penalizes broad or missing scopes around privileged tools.
Secret Handling Hygiene
3/4
Assesses secret-bearing tools, token leakage risk, and whether the public surface avoids obvious secret exposure.
Supply Chain Signal
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
Dynamic client registration materially improves connector setup.; OAuth interoperability should be strong.
Connector URL: https://docs.braingrid.ai/mcp
# Complete OAuth in the client when prompted.
# 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 Publish OAuth authorization-server metadata Clients need authorization-server metadata to discover issuer, endpoints, and DCR support. Publish /.well-known/oauth-authorization-server from your issuer and include registration_endpoint when supported.
Playbook
  • Publish `/.well-known/oauth-authorization-server` from the issuer.
  • Add `registration_endpoint` if DCR is supported.
  • Verify issuer, authorization, token, and jwks metadata are all reachable.
High Publish a complete server card Missing or incomplete server-card metadata weakens discovery, documentation, and trust signals. Serve /.well-known/mcp/server-card.json and include tools, prompts/resources, homepage, and support links.
Playbook
  • Publish `/.well-known/mcp/server-card.json`.
  • Include homepage, repository, support, tools, prompts/resources, and auth metadata.
  • Revalidate the server after publishing the card.
High Respond to auth mode changed Auth mode changed from unknown to oauth_supported. Document the new auth posture and confirm protected-resource and challenge metadata still match reality.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
High Respond to tool snapshot changed Tools were added, removed, or materially changed between the latest two validations. Publish a first-class changelog for tool additions, removals, and breaking schema changes.
Playbook
  • Review the tool snapshot diff for adds, removals, required-arg changes, and output-schema drift.
  • Publish a changelog before managed connector clients refresh their frozen tool snapshots.
  • Revalidate after the changelog and connector metadata are in sync.
High Respond to write-action surface expanded The number of high-risk write, delete, exec, or bulk-access tools increased on the latest run. Review the newly exposed write and destructive actions before publishing them broadly.
Playbook
  • Inspect the new write, delete, exec, or export tools for auth boundaries and confirmation semantics.
  • Add preview, dry-run, or explicit confirmation language where possible.
  • Delay public connector publication until the new blast radius is reviewed.
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 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 Respond to latest validation is degraded The server is reachable but at least one important behavior regressed. Resolve the regressed checks and review the latest validation diff.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
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
Utility Coverage 2/4 -2.0
Transport Compliance 2/4 -2.0
Spec Recency 2/4 -2.0
Schema Completeness 2/4 -2.0
Safety Transparency 2/4 -2.0
Registry Consistency 2/4 -2.0
Rate Limit Semantics 2/4 -2.0
Prompt Contract 2/4 -2.0
Execution Sandbox Safety 2/4 -2.0
Auth Operability 2/4 -2.0

Validation diff

Score delta
4.45
Summary changed
no
Tool delta
2
Prompt delta
0
Auth mode changed
yes
Write surface expanded
yes
Protocol regressed
no
Registry drift changed
no

Regressed checks: oauth_authorization_server, openid_configuration, server_card

Improved checks: connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_protected_resource, probe_noise_resilience, provenance_divergence_probe, resource_read, resources_list, tool_snapshot_probe, tools_list

ComponentPreviousLatestDelta
backward_compatibility_score2.04.02.0
adoption_signal_score2.03.831.83
registry_consistency_score3.52.0-1.5
trust_confidence_score1.752.941.19
connector_replay_score3.04.01.0
destructive_operation_safety_score2.03.01.0
least_privilege_scope_score2.03.01.0
result_shape_stability_score2.03.01.0

Tool snapshot diff & changelog

Snapshot changed
yes
Added tools
query_docs_filesystem_brain_grid search_brain_grid
Removed tools
none
Required-argument changes
ToolAdded required argsRemoved required args
No required-argument changes detected.
Output-schema drift
ToolPrevious propertiesLatest properties
No output-schema drift detected.

Connector replay

Status
OK
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
Missing
Advertised capabilities
none
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 Passes
  • oauth_protected_resourceOK
  • step_up_auth_probeWarning
Safe write flow with confirmation Degraded
  • action_safety_probeWarning

Registry & provenance divergence

Probe status
OK
Direct official match
no
Drift fields
none
FieldRegistryLive server card
Titlen/an/a
Versionn/an/a
Homepagen/an/a

Active alerts

Aliases & registry graph

IdentifierSourceCanonicalScore
awesome/braingrid-mcp awesome_mcp_servers yes 72.94

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
# Complete OAuth in the client when prompted.
# 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
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
2 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
2
Average Latency Ms
4245.28
Healthy Run Ratio Recent
0.0
Registry Presence Count
1
Active Alert Count
4
Watcher Count
0
Verified Claim
False
Taxonomy Tags
development, database, search, productivity
Score Trend
72.94, 68.49
Remediation Count
18
High Risk Tool Count
2
Destructive Tool Count
1
Exec Tool Count
2

Maintainer response quality

Score
16.67
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
Degraded
Validation profile
remote_mcp
Started
May 25, 2026 12:40:23 PM UTC
Latency
4043.0 ms

Failures

Checks

CheckStatusLatencyEvidence
action_safety_probe Warning n/a 2 high-risk, 1 destructive, 2 exec-capable tool(s); auth present; safeguards=1; confirmation=none.
advanced_capabilities_probe Warning n/a Only 2 capability signal(s): resource links, resources.
connector_publishability_probe Warning n/a Publishability blockers: server card.
connector_replay_probe OK n/a Backward compatible with no breaking tool-surface changes.
determinism_probe OK 339.0 ms Check completed
initialize OK 331.7 ms Protocol 2025-03-26
interactive_flow_probe OK n/a Check completed
oauth_authorization_server Error 169.9 ms Client error '404 Not Found' for url 'https://braingrid.main-kill-isr.mintlify.me/mcp/oauth/.well-known/oauth-authorization-server' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404
oauth_protected_resource OK 82.9 ms 1 authorization server(s)
official_registry_probe Warning n/a Check completed
openid_configuration Error 285.6 ms Client error '404 Not Found' for url 'https://braingrid.main-kill-isr.mintlify.me/mcp/oauth/.well-known/openid-configuration' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404
probe_noise_resilience OK 81.9 ms Fetched https://docs.braingrid.ai/robots.txt
prompt_get Missing n/a not advertised
prompts_list Missing 342.9 ms not supported
protocol_version_probe Warning n/a Claims 2025-03-26; 2 release(s) behind 2025-11-25.
provenance_divergence_probe OK n/a Check completed
request_association_probe Missing n/a No request-association capabilities were advertised.
resource_read OK 334.8 ms 1 resource content item(s) returned
resources_list OK 318.0 ms 1 resource item(s) exposed
server_card Error 368.9 ms Client error '404 Not Found' for url 'https://docs.braingrid.ai/.well-known/mcp/server-card.json' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404
session_resume_probe Warning n/a no session id
step_up_auth_probe Warning n/a Oauth detected.
tool_snapshot_probe OK n/a Check completed
tools_list OK 335.4 ms 2 tool(s) exposed
transport_compliance_probe Warning 336.6 ms Issues: missing session id, missing protocol header (bad protocol=400).
utility_coverage_probe Missing 363.8 ms No completions evidence; no pagination evidence; tasks missing.

Raw evidence view

Show raw JSON evidence
{
  "checks": {
    "action_safety_probe": {
      "details": {
        "auth_present": true,
        "confirmation_signals": [],
        "safeguard_count": 1,
        "summary": {
          "bulk_access_tools": 0,
          "capability_distribution": {
            "admin": 1,
            "delete": 1,
            "exec": 2,
            "filesystem": 2,
            "network": 1,
            "read": 2,
            "secrets": 1,
            "write": 2
          },
          "destructive_tools": 1,
          "egress_tools": 0,
          "exec_tools": 2,
          "high_risk_tools": 2,
          "risk_distribution": {
            "critical": 1,
            "high": 1,
            "low": 0,
            "medium": 0
          },
          "secret_tools": 1,
          "tool_count": 2
        }
      },
      "latency_ms": null,
      "status": "warning"
    },
    "advanced_capabilities_probe": {
      "details": {
        "capabilities": {
          "completions": false,
          "elicitation": false,
          "prompts": false,
          "resource_links": true,
          "resources": true,
          "roots": false,
          "sampling": false,
          "structured_outputs": false
        },
        "enabled": [
          "resource_links",
          "resources"
        ],
        "enabled_count": 2,
        "initialize_capability_keys": [
          "resources",
          "tools"
        ]
      },
      "latency_ms": null,
      "status": "warning"
    },
    "connector_publishability_probe": {
      "details": {
        "blockers": [
          "server_card"
        ],
        "criteria": {
          "action_safety": true,
          "auth_flow": true,
          "connector_replay": true,
          "initialize": true,
          "protocol_version": true,
          "remote_transport": true,
          "request_association": true,
          "server_card": false,
          "session_resume": true,
          "step_up_auth": true,
          "tool_surface": true,
          "tools_list": true,
          "transport_compliance": true
        },
        "high_risk_tools": 2,
        "tool_count": 2,
        "transport": "streamable-http"
      },
      "latency_ms": null,
      "status": "warning"
    },
    "connector_replay_probe": {
      "details": {
        "added_tools": [],
        "additive_output_changes": [],
        "backward_compatible": true,
        "output_breaks": [],
        "removed_tools": [],
        "required_arg_breaks": [],
        "would_break_after_refresh": false
      },
      "latency_ms": null,
      "status": "ok"
    },
    "determinism_probe": {
      "details": {
        "attempts": 2,
        "baseline_signature": "6d08a5ae9ccbd02b9ec78a460645897999f3491a2b0075f54de7527a6c3ae13b",
        "errors": [],
        "matches": 2,
        "stable_ratio": 1.0,
        "successful": 2
      },
      "latency_ms": 339.02,
      "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,
                "query_docs_filesystem_brain_grid": {
                  "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",
                  "operationId": "mintlify_default_query_docs_filesystem"
                },
                "search_brain_grid": {
                  "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",
                  "operationId": "mintlify_default_search"
                }
              }
            },
            "protocolVersion": "2025-03-26",
            "serverInfo": {
              "name": "BrainGrid",
              "version": "1.0.0"
            }
          }
        },
        "url": "https://docs.braingrid.ai/mcp"
      },
      "latency_ms": 331.74,
      "status": "ok"
    },
    "interactive_flow_probe": {
      "details": {
        "oauth_supported": true,
        "prompt_available": false,
        "risk_hits": [],
        "safe_hits": []
      },
      "latency_ms": null,
      "status": "ok"
    },
    "oauth_authorization_server": {
      "details": {
        "error": "Client error '404 Not Found' for url 'https://braingrid.main-kill-isr.mintlify.me/mcp/oauth/.well-known/oauth-authorization-server'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
        "url": "https://braingrid.main-kill-isr.mintlify.me/mcp/oauth/.well-known/oauth-authorization-server"
      },
      "latency_ms": 169.9,
      "status": "error"
    },
    "oauth_protected_resource": {
      "details": {
        "headers": {
          "content-type": "application/json",
          "strict-transport-security": "max-age=63072000"
        },
        "http_status": 200,
        "payload": {
          "authorization_servers": [
            "https://braingrid.main-kill-isr.mintlify.me/mcp/oauth"
          ],
          "resource": "https://braingrid.main-kill-isr.mintlify.me/mcp"
        },
        "url": "https://docs.braingrid.ai/.well-known/oauth-protected-resource"
      },
      "latency_ms": 82.87,
      "status": "ok"
    },
    "official_registry_probe": {
      "details": {
        "direct_match": false,
        "official_identifiers": [
          "io.github.martc03/federal-financial-intel",
          "ai.smithery/arjunkmrm-clock",
          "ai.smithery/keremurat-json",
          "ai.smithery/Pratiksha-Kanoja-magicslide-mcp-test",
          "io.github.TheNextGenNexus/real-estate-mcp-server",
          "io.github.human-pages-ai/humanpages",
          "io.github.gagandeeppra/mcp-observability-server",
          "ai.smithery/BigVik193-reddit-ads-mcp-api",
          "health.rhobimd.oss/shebe",
          "io.github.KaiErikNiermann/task-warrior-mcp"
        ],
        "official_peer_count": 10,
        "registry_source": "awesome_mcp_servers"
      },
      "latency_ms": null,
      "status": "warning"
    },
    "openid_configuration": {
      "details": {
        "error": "Client error '404 Not Found' for url 'https://braingrid.main-kill-isr.mintlify.me/mcp/oauth/.well-known/openid-configuration'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
        "url": "https://braingrid.main-kill-isr.mintlify.me/mcp/oauth/.well-known/openid-configuration"
      },
      "latency_ms": 285.63,
      "status": "error"
    },
    "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": 81.94,
      "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": 342.93,
      "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": 1,
        "registry_homepage": null,
        "registry_repository": null,
        "registry_title": null,
        "registry_version": null,
        "server_card_homepage": null,
        "server_card_repository": null,
        "server_card_title": null,
        "server_card_version": null
      },
      "latency_ms": null,
      "status": "ok"
    },
    "request_association_probe": {
      "details": {
        "reason": "no_request_association_capabilities_advertised"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "resource_read": {
      "details": {
        "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 from rough ideas, breaking down features into implementation tasks, managing projects with GitHub repositories, or building features with AI coding assistants like Claude Code, Cursor, or Windsurf. Reach for this skill when you need to transform vague concepts into detailed specifications and actionable tasks that AI agents can reliably execute.\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 vague feature ideas into detailed, actionable requirements and implementation tasks. It bridges the gap between high-level concepts and reliable AI-driven code execution by providing persistent codebase context, structured requirement refinement, and task-level guidance.\n\n**Key files and commands:**\n- `.braingrid/project.json` \u2014 links your local directory to a BrainGrid project\n- `braingrid` CLI \u2014 manage projects, requirements, and tasks from terminal\n- `braingrid init` \u2014 initialize a project in your repository\n- `braingrid specify --prompt \"...\"` \u2014 create AI-refined requirements\n- `braingrid requirement build REQ-X` \u2014 fetch full implementation plan\n- `braingrid task update --status COMPLETED` \u2014 track progress\n- MCP server integration \u2014 use BrainGrid tools directly in Claude Code, Cursor, Windsurf, or Codex\n\n**Primary docs:** https://docs.braingrid.ai\n\n## When to Use\n\nUse BrainGrid when:\n\n- **Planning features** \u2014 You have a rough idea and need AI to ask clarifying questions and structure it into a detailed requirement with acceptance criteria\n- **Breaking down work** \u2014 A requirement exists but needs to be split into specific, AI-ready implementation tasks\n- **Managing multi-repo projects** \u2014 You need to organize requirements across multiple GitHub repositories with automatic codebase analysis\n- **Building with AI agents** \u2014 You're using Claude Code, Cursor, Windsurf, or other MCP-compatible tools and want them to have structured task context\n- **Tracking implementation progress** \u2014 You need to mark tasks as in-progress or completed and maintain a clear status across your team\n- **Reviewing PRs against requirements** \u2014 You want AI-powered acceptance reviews that validate code against requirement criteria\n- **Capturing ideas before building** \u2014 You want to save rough concepts as \"Ideas\" before committing them to your backlog\n\nDo **not** use BrainGrid for: authentication setup, account management, billing, or dashboard-only operations.\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 current directory to project\nbraingrid status                   # Check auth and project context\n```\n\n### Core Workflow Commands\n\n| Task | Command | Notes |\n|------|---------|-------|\n| Create requirement from idea | `braingrid specify --prompt \"...\"` | AI refines your prompt into structured requirement |\n| View requirement details | `braingrid requirement show REQ-123` | Auto-detects from branch name if available |\n| Get full build plan | `braingrid requirement build REQ-123 --format markdown` | Markdown format best for AI agents |\n| List all tasks | `braingrid task list -r REQ-123` | Shows all tasks for a requirement |\n| View task details | `braingrid task show TASK-456` | Auto-detects first in-progress task if no ID given |\n| Mark task complete | `braingrid task update --status COMPLETED` | Auto-detects current task from branch |\n| Create git branch | `braingrid requirement create-branch REQ-123` | Auto-generates `{username}/REQ-123-slugified-name` |\n| Review PR | `braingrid requirement review` | Auto-detects PR from current branch |\n\n### Output Formats\n\nAll commands support `--format` flag:\n- `table` (default) \u2014 human-readable terminal output\n- `json` \u2014 machine-readable for scripting\n- `markdown` \u2014 optimized for AI agents\n- `xml` \u2014 enterprise integrations\n\nExample: `braingrid requirement build REQ-123 --format markdown`\n\n### ID Format Flexibility\n\nAll commands accept multiple formats (use whichever is convenient):\n- Canonical: `REQ-123`, `TASK-456`, `PROJ-789`\n- Lowercase: `req-123`, `task-456`, `proj-789`\n- Numeric only: `123`, `456`, `789`\n- Full UUID: `550e8400-e29b-41d4-a716-446655440000`\n\n### Status Flows\n\n**Requirements:** `IDEA \u2192 PLANNED \u2192 IN_PROGRESS \u2192 REVIEW \u2192 COMPLETED` (or `CANCELLED`)\n\n**Tasks:** `PLANNED \u2192 IN_PROGRESS \u2192 COMPLETED` (or `CANCELLED`)\n\n### Auto-Detection Features\n\n- **Project detection** \u2014 Reads `.braingrid/project.json` automatically\n- **Branch-based requirement** \u2014 Extracts `REQ-123` from branch names like `feature/REQ-123-description`\n- **Task auto-detection** \u2014 `task show` and `task update` work without task ID; uses first in-progress or planned task\n\n## Decision Guidance\n\n### When to Use CLI vs MCP Server\n\n| Scenario | Use CLI | Use MCP |\n|----------|---------|---------|\n| Running commands from terminal | \u2713 | \u2014 |\n| Working in Claude Code, Cursor, Windsurf | \u2713 | \u2713 (preferred for native integration) |\n| Web-based environment (no terminal) | \u2014 | \u2713 |\n| Need to script custom workflows | \u2713 | \u2014 |\n| Want to minimize context overhead | \u2713 | \u2014 |\n| Prefer tool-based integration | \u2014 | \u2713 |\n\n**Recommendation:** Use CLI for most workflows. Use MCP when working in an environment that doesn't support CLI or when you prefer native tool integration.\n\n### When to Create vs Capture Requirements\n\n| Approach | Use When | Command |\n|----------|----------|---------|\n| **Create** (AI refinement) | You have a rough idea or brief description | `braingrid specify --prompt \"...\"` |\n| **Capture** (pre-written) | You already have detailed content written | `braingrid requirement create --name \"...\" --content \"...\"` |\n\n**Best practice:** Use `specify` for rough ideas; let AI ask clarifying questions and structure the requirement. Use `capture` when you've already written detailed specs elsewhere.\n\n### When to Refine in Web App vs Break Down via MCP\n\n| Approach | Use When | Where |\n|----------|----------|-------|\n| **Web app refinement** | Requirement needs interactive clarification, team collaboration, or detailed editing | https://app.braingrid.ai |\n| **MCP breakdown** | You want to stay in your coding environment and generate tasks quickly | In Claude Code, Cursor, etc. |\n\n**Best practice:** Use web app for complex requirements needing refinement; use MCP for quick task generation on well-defined requirements.\n\n## Workflow\n\n### Typical Feature Development Cycle\n\n1. **Capture the idea**\n   - Run `braingrid specify --prompt \"Add dark mode toggle with theme persistence\"`\n   - AI asks clarifying questions; iterate until requirement is clear\n   - Requirement is created (e.g., `REQ-42`)\n\n2. **Refine and break down** (optional, in web app)\n   - Go to https://app.braingrid.ai and open REQ-42\n   - Work with requirements agent to add details, acceptance criteria, edge cases\n   - Agent breaks requirement into 5-10 specific implementation tasks\n\n3. **Create feature branch**\n   - Run `braingrid requirement create-branch REQ-42`\n   - Creates `{username}/REQ-42-dark-mode` on GitHub\n   - Check out locally: `git fetch && git checkout {username}/REQ-42-dark-mode`\n\n4. **Get build context**\n   - Run `braingrid requirement build REQ-42 --format markdown`\n   - Copy output into your AI coding tool (Claude Code, Cursor, etc.)\n   - Or use `/build REQ-42` slash command if integration is installed\n\n5. **Implement tasks**\n   - AI agent reads requirement and tasks\n   - Implements each task, updating status as it goes\n   - Run `braingrid task update --status COMPLETED` after each task\n\n6. **Review and validate**\n   - Create pull request on GitHub\n   - Run `braingrid requirement review` for AI-powered acceptance review\n   - Review validates PR against requirement's acceptance criteria\n\n7. **Track completion**\n   - Run `braingrid requirement show REQ-42` to see overall progress\n   - Status updates from `IN_PROGRESS` to `REVIEW` to `COMPLETED`\n\n### Quick Start (One-Minute Flow)\n\n```bash\n# 1. Initialize\nbraingrid init\n\n# 2. Create requirement from idea\nbraingrid specify --prompt \"Add user authentication with OAuth2\"\n\n# 3. Get implementation plan\nbraingrid requirement build REQ-1 --format markdown\n\n# 4. Copy output to your AI coding tool and start building\n```\n\n## Common Gotchas\n\n- **Missing `.braingrid/project.json`** \u2014 Run `braingrid init` in your repository root. This file links your local directory to a BrainGrid project. Without it, CLI commands won't know which project to use.\n\n- **Branch name auto-detection fails** \u2014 Branch names must contain `REQ-123` format (e.g., `feature/REQ-123-description`). If your branch doesn't include the requirement ID, commands won't auto-detect. Create the branch with `braingrid requirement create-branch` to ensure correct naming.\n\n- **Task auto-detection picks wrong task** \u2014 `task show` and `task update` without a task ID use the first in-progress task, or first planned task if none are in-progress. If you have multiple tasks in the same state, explicitly specify the task ID: `braingrid task show TASK-456`.\n\n- **MCP authentication fails** \u2014 After installing MCP in Claude Code, Cursor, etc., you'll see \"Needs login\" or \"Disconnected\". Click the message and authenticate via browser. Once authenticated, restart your editor.\n\n- **Requirement shows no tasks** \u2014 Requirements must be broken down into tasks before building. Either:\n  - Use the web app requirements agent to break it down (recommended for complex requirements)\n  - Run `braingrid breakdown_project_requirement REQ-123` via MCP to auto-generate tasks\n\n- **CLI commands timeout on large codebases** \u2014 BrainGrid analyzes your codebase on first project creation. Large repos may take a few minutes. Check https://app.braingrid.ai to see analysis progress.\n\n- **Deleting a project is permanent** \u2014 `braingrid project delete PROJ-123` removes all requirements and tasks. Use `--force` to skip confirmation, but understand this cannot be undone.\n\n- **Status line not showing in Claude Code** \u2014 The status line (e.g., `PROJ-3 > REQ-128 [2/5]`) requires `.claude/statusline.sh` to be created by `braingrid setup claude-code`. If missing, re-run setup.\n\n- **Slash commands not appearing** \u2014 After running `braingrid setup cursor` or `braingrid setup claude-code`, restart your editor. Commands appear in the `/` menu after restart.\n\n## Verification Checklist\n\nBefore submitting work or marking a requirement complete:\n\n- [ ] **Project is initialized** \u2014 `.braingrid/project.json` exists in repository root\n- [ ] **Requirement has tasks** \u2014 Run `braingrid task list -r REQ-X` and confirm tasks exist (not empty)\n- [ ] **All tasks marked complete** \u2014 Run `braingrid requirement show REQ-X` and verify all tasks show `COMPLETED` status\n- [ ] **Branch is created and pushed** \u2014 Feature branch exists on GitHub (created via `braingrid requirement create-branch`)\n- [ ] **PR is open** \u2014 Pull request links to the feature branch\n- [ ] **Acceptance review passed** \u2014 Run `braingrid requirement review` and confirm PR meets acceptance criteria\n- [ ] **Requirement status updated** \u2014 Run `braingrid requirement update REQ-X --status COMPLETED` to mark requirement done\n- [ ] **Code is committed** \u2014 All changes are committed and pushed to the feature branch\n\n## Resources\n\n**Comprehensive navigation:** https://docs.braingrid.ai/llms.txt \u2014 Full page-by-page listing for agent navigation\n\n**Critical documentation:**\n- [CLI Command Reference](https://docs.braingrid.ai/cli/commands) \u2014 Complete command reference with all options\n- [MCP Server Usage](https://docs.braingrid.ai/mcp-server/usage) \u2014 How to use BrainGrid tools in Claude Code, Cursor, Windsurf\n- [Quickstart Guide](https://docs.braingrid.ai/quickstart) \u2014 Step-by-step walkthrough of the full workflow\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": 334.77,
      "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 from rough ideas, breaking down features into implementation tasks, managing projects with GitHub repositories, or building features with AI coding assistants like Claude Code, Cursor, or Windsurf. Reach for this skill when you need to transform vague concepts into detailed specifications and actionable tasks that AI agents can reliably execute.",
                "mimeType": "text/markdown",
                "name": "braingrid",
                "uri": "mintlify://skills/braingrid"
              }
            ]
          }
        },
        "url": "https://docs.braingrid.ai/mcp"
      },
      "latency_ms": 317.99,
      "status": "ok"
    },
    "server_card": {
      "details": {
        "error": "Client error '404 Not Found' for url 'https://docs.braingrid.ai/.well-known/mcp/server-card.json'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
        "url": "https://docs.braingrid.ai/.well-known/mcp/server-card.json"
      },
      "latency_ms": 368.92,
      "status": "error"
    },
    "session_resume_probe": {
      "details": {
        "protocol_version": "2025-03-26",
        "reason": "no_session_id",
        "resume_expected": true,
        "transport": "streamable-http"
      },
      "latency_ms": null,
      "status": "warning"
    },
    "step_up_auth_probe": {
      "details": {
        "auth_required_checks": [],
        "broad_scopes": [],
        "challenge_headers": [],
        "minimal_scope_documented": false,
        "oauth_present": true,
        "scope_specificity_ratio": 0.0,
        "step_up_signals": [],
        "supported_scopes": []
      },
      "latency_ms": null,
      "status": "warning"
    },
    "tool_snapshot_probe": {
      "details": {
        "added": [],
        "changed_outputs": [],
        "current_tool_count": 2,
        "previous_tool_count": 2,
        "removed": [],
        "similarity": 1.0
      },
      "latency_ms": null,
      "status": "ok"
    },
    "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": [
              {
                "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"
              },
              {
                "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"
              }
            ]
          }
        },
        "url": "https://docs.braingrid.ai/mcp"
      },
      "latency_ms": 335.43,
      "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": 336.55,
      "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": 363.76,
      "status": "missing"
    }
  },
  "failures": {
    "oauth_authorization_server": {
      "error": "Client error '404 Not Found' for url 'https://braingrid.main-kill-isr.mintlify.me/mcp/oauth/.well-known/oauth-authorization-server'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
      "url": "https://braingrid.main-kill-isr.mintlify.me/mcp/oauth/.well-known/oauth-authorization-server"
    },
    "openid_configuration": {
      "error": "Client error '404 Not Found' for url 'https://braingrid.main-kill-isr.mintlify.me/mcp/oauth/.well-known/openid-configuration'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
      "url": "https://braingrid.main-kill-isr.mintlify.me/mcp/oauth/.well-known/openid-configuration"
    },
    "server_card": {
      "error": "Client error '404 Not Found' for url 'https://docs.braingrid.ai/.well-known/mcp/server-card.json'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
      "url": "https://docs.braingrid.ai/.well-known/mcp/server-card.json"
    }
  },
  "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
0%
Freshness
1.3h
TimestampStatusScoreLatencyTools
May 25, 2026 12:40:27 PM UTC Degraded 72.9 4043.0 ms 2
May 25, 2026 03:04:15 AM UTC Degraded 68.5 4447.6 ms 0

Validation timeline

ValidatedSummaryScoreProtocolAuth modeToolsHigh-risk toolsChanges
May 25, 2026 12:40:27 PM UTC Degraded 72.9 2025-03-26 oauth_supported 2 2 auth_mode_changed write_surface_expanded tool_snapshot_changed
May 25, 2026 03:04:15 AM UTC Degraded 68.5 unknown unknown 0 0 none

Recent validation runs

StartedStatusSummaryLatencyChecks
May 25, 2026 12:40:23 PM UTC Completed Degraded 4043.0 ms action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe
May 25, 2026 03:04:11 AM UTC Completed Degraded 4447.6 ms