Brainiall Documents
REMOTE · API.BRAINIALL.COM · SCANNED SEP 21
High-fidelity PDF to structured Markdown conversion and document field extraction.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
How do I install the Brainiall Documents MCP server?
Brainiall Documents is a hosted endpoint at https://api.brainiall.com/mcp/documents/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.brainiall.com
claude mcp add --transport http com-brainiall-documents 'https://api.brainiall.com/mcp/documents/mcp'
{
"mcpServers": {
"com-brainiall-documents": {
"url": "https://api.brainiall.com/mcp/documents/mcp"
}
}
} {
"servers": {
"com-brainiall-documents": {
"type": "http",
"url": "https://api.brainiall.com/mcp/documents/mcp"
}
}
} [mcp_servers.com-brainiall-documents] url = "https://api.brainiall.com/mcp/documents/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-brainiall-documents": {
"type": "remote",
"url": "https://api.brainiall.com/mcp/documents/mcp",
"enabled": true
}
}
} openclaw mcp add com-brainiall-documents --url 'https://api.brainiall.com/mcp/documents/mcp' --transport streamable-http
mcp_servers:
com-brainiall-documents:
url: "https://api.brainiall.com/mcp/documents/mcp" {
"McpServers": {
"com-brainiall-documents": {
"Transport": "http",
"Url": "https://api.brainiall.com/mcp/documents/mcp"
}
}
} assistant mcp add com-brainiall-documents -t streamable-http -u 'https://api.brainiall.com/mcp/documents/mcp'
{
"mcpServers": {
"com-brainiall-documents": {
"type": "http",
"url": "https://api.brainiall.com/mcp/documents/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 18 Sept 26 +7
- Endpoint reachability: unreachable → behind authorisation ▼ security
- Authorization: unverified → fail ▼ security
- Transport: fail → unverified ▼ security
- TLS certificate: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Tool safety: Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools. security
- Tool coverage: Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools. functional
- Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it. functional
- Capabilities: Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. functional
- 17 Sept 26 −7
The score moved with no change recorded against any check. We would rather say so than guess.
- 15 Sept 26 0
- Endpoint reachability: behind authorisation → unreachable ▼ security
- Transport: unverified → fail ▼ security
- Authorization: fail → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Tool safety: Tool safety not yet verified: we couldn't read the endpoint's tools. security
- Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools. functional
- Capabilities: Capabilities not yet verified: we couldn't read the endpoint's capabilities. functional
- Schema quality: Schema not yet verified: we couldn't read the endpoint's schema. functional
- 13 Sept 26 +4
- Endpoint reachability: unreachable → behind authorisation ▼ security
- Authorization: unverified → fail ▼ security
- Transport: fail → unverified ▼ security
- TLS certificate: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Tool safety: Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools. security
- Tool coverage: Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools. functional
- Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it. functional
- Capabilities: Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. functional
- 12 Sept 26 −16
The score moved with no change recorded against any check. We would rather say so than guess.
- 11 Sept 26 −16
The score moved with no change recorded against any check. We would rather say so than guess.
- 10 Sept 26 −16
The score moved with no change recorded against any check. We would rather say so than guess.
- 8 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.40 → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Probed https://api.brainiall.com/mcp/documents/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.brainiall.com | CN=YE1,O=Let's Encrypt,C=US | 17 Sept 2026 | 16 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 67be4a7733d1cf211aca7804ebcd6817fe5 |
| SANs: api.brainiall.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.brainiall.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| brainiall.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer resource_metadata="https://api.brainiall.com/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://api.brainiall.com/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| www-authenticate | Bearer resource_metadata="https://api.brainiall.com/.well-known/oauth-protected-resource" |
Protected resource metadata
| Document | https://api.brainiall.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Problem | metadata_incomplete |
| Resource | https://api.brainiall.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.brainiall.com/mcp/documents/mcp | Auth required | 401 | |
| http (plaintext) | http://api.brainiall.com/mcp/documents/mcp | HTTPS enforced | 308 | https://api.brainiall.com/mcp/documents/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_document_service Check Document Service ~57
Check whether document conversion and extraction are available. Use this before a workflow or when another document tool reports a temporary availability problem. No document input is required. Returns: A dictionary with status='healthy', or an actionable error object.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
extract_document_fields Extract Document Fields ~164
Extract structured fields and full text from a document image. Use this for invoices, receipts, forms, and similar PNG or JPEG images when the agent needs named fields rather than Markdown. PDF input is intentionally rejected; use pdf_to_markdown for PDFs. Returns: A dictionary containing request metadata, extracted fields, and text, or an actionable error object on failure.
| Name | Type | Req | Description |
|---|---|---|---|
| doc_type | string | – | Document type that guides field extraction, such as 'invoice' (default), 'receipt', or 'form'. |
| image_base64 | – | – | Base64-encoded PNG or JPEG bytes. Provide this or url, never both. |
| url | – | – | Public URL pointing directly to a PNG or JPEG document image. Provide this or image_base64, never both. |
No output schema declared.
No examples provided.
pdf_to_markdown Convert PDF to Markdown ~151
Convert a PDF into readable Markdown for analysis and retrieval. Use this when an agent needs the text, headings, tables, and document structure from a PDF. Supply exactly one source: a public URL or base64 PDF bytes. The optional page range is useful for large documents. Returns: Markdown text on success, or an actionable error object on failure.
| Name | Type | Req | Description |
|---|---|---|---|
| page_range | – | – | Optional pages to convert, such as '1-5'. Omit to convert the entire PDF. |
| pdf_base64 | – | – | Base64-encoded PDF bytes. Provide this or url, never both. |
| url | – | – | Public URL pointing directly to a PDF. Provide this or pdf_base64, never both. |
No output schema declared.
No examples provided.
What is the Brainiall Documents MCP server?
Brainiall Documents is an MCP server listed in the public MCP registry as com.brainiall/documents. High-fidelity PDF to structured Markdown conversion and document field extraction. This page covers its hosted endpoint (https://api.brainiall.com/mcp/documents/mcp).
Is the Brainiall Documents MCP server safe to use?
Brainiall Documents scores 36 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Brainiall Documents MCP server expose?
Brainiall Documents exposes 3 tools: pdf_to_markdown, extract_document_fields, check_document_service. Their descriptions and schemas cost roughly 372 tokens of context every time the server is loaded.
Does the Brainiall Documents MCP server require authentication?
Yes. Brainiall Documents asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Brainiall Documents MCP server still maintained?
Brainiall Documents is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.