Burs-IA
REMOTE · BURS-IA-MCP-ADAPTER-PRODUCTION.UP.RAILWAY.APP · SCANNED SEP 29
Burs-IA public MCP entry point for capability discovery, bounded routing and interoperability.
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 307 tokens (~38/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Burs-IA MCP server?
Burs-IA is a hosted endpoint at https://burs-ia-mcp-adapter-production.up.railway.app/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 · burs-ia-mcp-adapter-production.up.railway.app
claude mcp add --transport http soyeladice-svg-bursia 'https://burs-ia-mcp-adapter-production.up.railway.app/mcp'
{
"mcpServers": {
"soyeladice-svg-bursia": {
"url": "https://burs-ia-mcp-adapter-production.up.railway.app/mcp"
}
}
} {
"servers": {
"soyeladice-svg-bursia": {
"type": "http",
"url": "https://burs-ia-mcp-adapter-production.up.railway.app/mcp"
}
}
} [mcp_servers.soyeladice-svg-bursia] url = "https://burs-ia-mcp-adapter-production.up.railway.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"soyeladice-svg-bursia": {
"type": "remote",
"url": "https://burs-ia-mcp-adapter-production.up.railway.app/mcp",
"enabled": true
}
}
} openclaw mcp add soyeladice-svg-bursia --url 'https://burs-ia-mcp-adapter-production.up.railway.app/mcp' --transport streamable-http
mcp_servers:
soyeladice-svg-bursia:
url: "https://burs-ia-mcp-adapter-production.up.railway.app/mcp" {
"McpServers": {
"soyeladice-svg-bursia": {
"Transport": "http",
"Url": "https://burs-ia-mcp-adapter-production.up.railway.app/mcp"
}
}
} assistant mcp add soyeladice-svg-bursia -t streamable-http -u 'https://burs-ia-mcp-adapter-production.up.railway.app/mcp'
{
"mcpServers": {
"soyeladice-svg-bursia": {
"type": "http",
"url": "https://burs-ia-mcp-adapter-production.up.railway.app/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.
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “bursia_status” rewrote its description, which is the text the model reads security
- Tool “capability_triage” rewrote its description, which is the text the model reads security
- Tool “discover_capabilities” rewrote its description, which is the text the model reads security
- Schema quality: 34 → 38 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Schema quality: fair → good functional
- Server version: 0.3.0 → 0.6.1 functional
- New tool “agent_collaboration_request” functional
- New tool “human_bridge_request” functional
- New tool “human_oversight_policy” functional
- New tool “outbound_gateway_policy” functional
- New tool “prepare_outbound_invitation” functional
- 18 Sept 26 59
First indexed and scored.
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 29 Sept 2026 · Probed https://burs-ia-mcp-adapter-production.up.railway.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.up.railway.app | CN=YE2,O=Let's Encrypt,C=US | 27 Sept 2026 | 26 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 618edc56941aa1165ddb080bf9f799eb7c1 |
| SANs: *.up.railway.app, up.railway.app | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 burs-ia-mcp-adapter-production.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| railway.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://burs-ia-mcp-adapter-production.up.railway.app/mcp | Verified | 200 | |
| http (plaintext) | http://burs-ia-mcp-adapter-production.up.railway.app/mcp | HTTPS enforced | 301 | https://burs-ia-mcp-adapter-production.up.railway.app/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 →
agent_collaboration_request ~41
Prepare a privacy-minimal agent-to-agent collaboration request without contacting an external agent automatically.
| Name | Type | Req | Description |
|---|---|---|---|
| protocols | array | – | – |
| request | string | yes | – |
No output schema declared.
No examples provided.
bursia_status ~23
Return public Bursia operational status, discovery surfaces and oversight policy.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
capability_triage ~35
Classify a request into a public Bursia capability lane and return the next safe action.
| Name | Type | Req | Description |
|---|---|---|---|
| request | string | yes | – |
No output schema declared.
No examples provided.
discover_capabilities ~27
List Bursia public capabilities and compatible entry points.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | – |
No output schema declared.
No examples provided.
human_bridge_request ~40
Prepare an authorized human-in-the-loop handoff request. No human is contacted automatically.
| Name | Type | Req | Description |
|---|---|---|---|
| authorization | string | – | – |
| request | string | yes | – |
No output schema declared.
No examples provided.
human_oversight_policy ~24
Return Bursia bounded-autonomy and human-supervision policy.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
outbound_gateway_policy ~29
Return Bursia Beacon outbound discovery policy. External sends require target allowlisting and explicit human approval.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
prepare_outbound_invitation ~56
Prepare, but do not send, a Bursia invitation candidate for a documented machine endpoint or opt-in recipient.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | – |
| permissionBasis | string | yes | – |
| target | string | yes | – |
No output schema declared.
No examples provided.
What is the Burs-IA MCP server?
Burs-IA is an MCP server listed in the public MCP registry as io.github.soyeladice-svg/bursia. Burs-IA public MCP entry point for capability discovery, bounded routing and interoperability. This page covers its hosted endpoint (https://burs-ia-mcp-adapter-production.up.railway.app/mcp).
Is the Burs-IA MCP server safe to use?
Burs-IA scores 65 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 Burs-IA MCP server expose?
Burs-IA exposes 8 tools: bursia_status, discover_capabilities, capability_triage, agent_collaboration_request, human_bridge_request, and 3 more. Their descriptions and schemas cost roughly 275 tokens of context every time the server is loaded.
Does the Burs-IA MCP server require authentication?
No. We connected to Burs-IA without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Burs-IA MCP server still maintained?
Burs-IA is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.