BRAINIAC API Integration Intelligence MCP server
software.brainiac/integrationbrainiac.softwarestreamable-httpv1.0.1Scanned
Paid API Integration Intelligence API via x402. Unpaid tool calls return 402.
8 tools: 6 change things and 2 only read.
- Reads private data · 1
- Reads text others write · 8
- Can send data out · 0
- 4 findings
Tools listed without sign-in. Remote posture
With Anlyon
6 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the BRAINIAC API Integration Intelligence MCP server can do
The BRAINIAC API Integration Intelligence MCP server is published by brainiac.software, a domain the MCP Registry verified. It has 8 tools. It can create or change data (6 tools: integration_json-schema-generate, integration_response-normalize, integration_payload-transform, integration_field-map-generate and 2 more), but cannot delete data. 2 tools only read.
1 tool reads private data (integration_contract-compare); 8 tools bring in text other people can write (integration_json-schema-generate, integration_json-schema-validate, integration_response-normalize and 5 more).
The fixed checks matched 4 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 20, 2026, version 1.0.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
8 tools
Changes things 6Claude Code: ask
integration_diagnoseGenerate a schema from examples, validate the payload, map fields that exist, compare contracts, and apply documented transforms.Reads text others write1 finding
Why it is in this group
- The description's first verb is "generate": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "integration_diagnose" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "generate": a word for a change.
Description, as the server wrote it Generate a schema from examples, validate the payload, map fields that exist, compare contracts, and apply documented transforms. No external API is called. Price $0.12 USDC. POST /api/v1/integration/diagnose. An unpaid call returns the x402 payment terms and does not run.
Annotations the server declares
- title: Diagnose an integration
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
integration_field-map-generateMap a path that exists on both sides, or a field name that matches one leaf on each side after splitting camel case and snake case.Reads text others write1 finding
Why it is in this group
- The name "integration_field-map-generate" says "generate": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "integration_field-map-generate" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "integration_field-map-generate" says "generate": a word for a change.
Description, as the server wrote it Map a path that exists on both sides, or a field name that matches one leaf on each side after splitting camel case and snake case. No value is copied. Price $0.05 USDC. POST /api/v1/integration/field-map-generate. An unpaid call returns the x402 payment terms and does not run.
Annotations the server declares
- title: Generate a field map
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
integration_json-schema-generateBuild a schema from supplied examples.Reads text others write1 finding
Why it is in this group
- The name "integration_json-schema-generate" says "generate": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "integration_json-schema-generate" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "integration_json-schema-generate" says "generate": a word for a change.
Description, as the server wrote it Build a schema from supplied examples. Required properties are keys present on every example. Whole numbers are integer. Additional properties stay allowed. Price $0.04 USDC. POST /api/v1/integration/json-schema-generate. An unpaid call returns the x402 payment terms and does not run.
Annotations the server declares
- title: Generate a JSON schema
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
integration_payload-transformApply rename, copy, pick, omit, cast, and default in order.Reads text others write1 finding
Why it is in this group
- The description's first verb is "apply": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "integration_payload-transform" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "apply": a word for a change.
Description, as the server wrote it Apply rename, copy, pick, omit, cast, and default in order. A missing source is reported and not invented. A default is written only when the path is absent. Price $0.05 USDC. POST /api/v1/integration/payload-transform. An unpaid call returns the x402 payment terms and does not run.
Annotations the server declares
- title: Transform a payload
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
integration_response-normalizeTrim string edges and sort object keys.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Trim string edges and sort object keys. Types are not changed, fields are not removed, and each change is listed. Price $0.03 USDC. POST /api/v1/integration/response-normalize. An unpaid call returns the x402 payment terms and does not run.
Annotations the server declares
- title: Normalize an API response
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
integration_version-compatibility-checkOrder dotted numeric versions and compare the supplied schemas.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Order dotted numeric versions and compare the supplied schemas. A version number alone is not treated as compatible. The payload is checked against the later schema. Price $0.04 USDC. POST /api/v1/integration/version-compatibility-check. An unpaid call returns the x402 payment terms and does not run.
Annotations the server declares
- title: Check version compatibility
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Only reads 2Show 2 read-only tools
integration_contract-compareList schema changes.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "integration_contract-compare" says "compare": a word for reading.
What it can reach
- private-dataThe input names a file (input.file), and the tool reads: it reads files.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it List schema changes. A change is labeled breaking or non-breaking only when side is request or response. Title and description are ignored. Price $0.05 USDC. POST /api/v1/integration/contract-compare. An unpaid call returns the x402 payment terms and does not run.
Annotations the server declares
- title: Compare API contracts
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
integration_json-schema-validateCheck a payload against a supplied schema using the documented subset.Reads text others writeNo findings
Why it is in this group
- The name "integration_json-schema-validate" says "validate": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Check a payload against a supplied schema using the documented subset. Each failure has a JSON pointer. Unsupported keywords are reported and not applied. Price $0.04 USDC. POST /api/v1/integration/json-schema-validate. An unpaid call returns the x402 payment terms and does not run.
Annotations the server declares
- title: Validate a payload
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write8
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:33 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 6
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 6 tools that change things (6 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://www.brainiac.software/mcp/integration: tools/list returned 8 tools to an anonymous client, including integration_json-schema-generate (write), integration_response-normalize (write), integration_payload-transform (write), integration_field-map-generate (write), integration_version-compatibility-check (write) and 1 more
Findings
Matches of fixed checks, with the text they matched.
The server marks "integration_json-schema-generate" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "integration_json-schema-generate" says "generate": a word for a change.
The server marks "integration_payload-transform" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "apply": a word for a change.
The server marks "integration_field-map-generate" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "integration_field-map-generate" says "generate": a word for a change.
The server marks "integration_diagnose" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "generate": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools8 changed.~8 changedView diff
- Changed:integration_contract-compareOnly readsinputSchemaannotations
- Changed:integration_diagnoseChanges thingsinputSchemaannotations
- Changed:integration_field-map-generateChanges thingsinputSchemaannotations
- Changed:integration_json-schema-generateChanges thingsinputSchemaannotations
- Changed:integration_json-schema-validateOnly readsinputSchemaannotations
- Changed:integration_payload-transformChanges thingsinputSchemaannotations
- Changed:integration_response-normalizeChanges thingsinputSchemaannotations
- Changed:integration_version-compatibility-checkChanges thingsinputSchemaannotations
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http integration https://www.brainiac.software/mcp/integrationclaude mcp add --transport http integration https://www.brainiac.software/mcp/integrationRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__integration__integration_json-schema-validate",
"mcp__integration__integration_contract-compare"
],
"ask": [
"mcp__integration__integration_json-schema-generate",
"mcp__integration__integration_response-normalize",
"mcp__integration__integration_payload-transform",
"mcp__integration__integration_field-map-generate",
"mcp__integration__integration_version-compatibility-check",
"mcp__integration__integration_diagnose"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as integration. Review it before you use it.
Capability tags behind 8 rules
- mcp__integration__integration_json-schema-generate untrusted-input
- mcp__integration__integration_json-schema-validate untrusted-input
- mcp__integration__integration_response-normalize untrusted-input
- mcp__integration__integration_payload-transform untrusted-input
- mcp__integration__integration_field-map-generate untrusted-input
- mcp__integration__integration_contract-compare private-data, untrusted-input
- mcp__integration__integration_version-compatibility-check untrusted-input
- mcp__integration__integration_diagnose untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/software.brainiac/integration/verify?hash=d88a71b457764b35a0cd548ac9e15fe9857a355fcb6bf565e79ca149ff906cf9" | jq -e '.changed == false'Pinned hash d88a71b45776, from Nov 20, 2026, 01:19 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/software.brainiac/integration/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/software.brainiac/integration)Source: MCP Registry. Synced Nov 20, 2026, 01:18 UTC.
BRAINIAC API Integration Intelligence MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the BRAINIAC API Integration Intelligence MCP server safe?
- No scan can promise that. What its definitions show: 8 tools, 6 of which can change, send or delete something, and 4 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the BRAINIAC API Integration Intelligence MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the BRAINIAC API Integration Intelligence MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the BRAINIAC API Integration Intelligence MCP server have?
- 8 tools: 6 write, 2 read. integration_json-schema-generate, integration_response-normalize, integration_payload-transform, integration_field-map-generate, integration_version-compatibility-check, integration_diagnose, integration_json-schema-validate and integration_contract-compare.
Does the BRAINIAC API Integration Intelligence MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the BRAINIAC API Integration Intelligence MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the BRAINIAC API Integration Intelligence MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.