MCP servers › tech.atomadic › atomadic
MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23
tech.atomadic/atomadic
Atomadic MCP: 68 deterministic tools for agent identity, escrow, SLA, EU AI Act compliance. — the publisher's description
Summary
tech.atomadic/atomadic is a remote MCP server listed in the official MCP registry at version 0.6.9. On 2026-10-23 ProtocolProbe connected to it in read-only mode and read its inventory: 68 tools, 0 resources and 0 prompts.
Record checks
1 of 2 record checks met · 7 do not apply
- met: Registry entry is active and says how to run it
- not met: Source repository link opens
- not applicable: Repository is not archived
- not applicable: Code pushed to the repository in the 90 days before our check
- not applicable: Repository publishes a security policy (SECURITY.md)
- not applicable: Package names its licence with a standard (SPDX) identifier
- not applicable: The version the registry lists can be installed and is not withdrawn
- not applicable: npm package carries build provenance (attestation)
- not applicable: No known critical or high advisory in the package or its dependencies
- Not ranked by downloads: a remote server publishes no download figure
- Not ranked by stars: no public GitHub repository
From public records, not a safety rating. Each check with its reason · Is it safe to install?
Key facts
- Runs
- remote (hosted by the publisher)
- Transport
- streamable HTTP
- Sign-in
- none needed to open a session
- Tools
- 68
- Described as changing data
- 15 of 68 toolsAI-classified
- Topic
- securityAI-classified
- Pricing
- freemiumAI-classified
- Last tested
- 2026-10-23
Observed fact
This server accepted a session without any credential and lists 1 tool whose name or declaration suggests it changes data (escrow_create). That is our reading of the names; we did not call it. Source: our connection, 2026-10-23.
Worth knowing before you connect it
- 15 tools are described as changing something (agents_register, compliance_incident, compliance_oversight, …): our AI model's reading of the descriptions, not something we tested, and the server opened a session without any credential. We did not call them.
Each line comes from a section below, with its source and date.
How fresh this is
- Live-tested
- yes, a real session (not a text-only review)
- Last tested
- 2026-10-23
- Mode
- read-only (no tool calls)
- Latest version
- 0.6.9, published 2026-10-17 (registry, as of the 2026-10-23 snapshot)
- First listed version
- 2026-10-17 (earliest version still in the registry; older removed versions would be earlier)
- Registry data
- snapshot 2026-10-23
- Package and repository
- checked 2026-10-23
- Engine
- mcp-runtime-engine@0.1.0 · sdk@1.32.0
Changes since the last refresh
New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 0.6.9 (published 2026-10-17).
Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.
What it is
What does this server offer?
Observed inventory15 of 68 tools are described as changing something (creating, editing, deleting, sending or running). For 9 the reading was uncertain, so no mark is shown.
- murmuration
“START HERE (free, no key).”
1 input
agent_idstring“Optional stable id to track your onboarding state across calls.”
- agents_contradictionreads or searches
“[agents] Detect contradictions in agent outputs”
1 input, 1 required
statementsarrayrequired
- agents_intent_classifyreads or searches
“[agents] Agent intent classification”
1 input, 1 required
textstringrequired
- agents_planon 1 other server
“[agents] Autonomous agent goal planning”
2 inputs, 1 required
goalstringrequiredconstraintsobject“Optional constraints for the plan (e.g., time limits, resource caps)”
- agents_registercreates or changes datadescribed as changing data
“[agents] Register an agent”
2 inputs, 2 required
agent_idstringrequiredcapabilitiesarrayrequired
- agents_reputationreads or searches
“[agents] Agent reputation and trust score”
1 input, 1 required
agent_idstringrequired
- agents_semantic_diffcalculates or converts
“[agents] Semantic diff between agent outputs”
3 inputs, 2 required
output_astringrequiredoutput_bstringrequiredcontextstring
- agents_topologyreads or searches
“[agents] Live swarm topology”
Takes no inputs.
“[security] GDPR/CCPA compliance gate”
3 inputs, 3 required
data_typestringrequiredjurisdictionstringrequiredoperationstringrequired
- compliance_eu_ai_actreads or searches
“[security] EU AI Act compliance certificate”
3 inputs, 3 required
system_idstringrequiredrisk_categorystringrequiredintended_purposestringrequired
- compliance_explainreads or searches
“[security] Explainability certificate (XPL-100-ExplainBound)”
3 inputs, 3 required
model_idstringrequireddecision_idstringrequiredsubject_contextobjectrequired
- compliance_fairnessreads or searches
“[security] Fairness proof (FNS-100-FairnessBound)”
4 inputs, 4 required
model_idstringrequireddataset_idstringrequiredprotected_attrsarrayrequiredmetricstringrequired
Show 56 more tools
- compliance_incidentdescribed as changing data
“[security] Report compliance incident”
4 inputs, 4 required
system_idstringrequiredseveritystringrequireddescriptionstringrequiredaffected_usersintegerrequired
- compliance_incidentsreads or searches
“[security] Incident registry”
1 input, 1 required
system_idstringrequired
- compliance_lineagereads or searches
“[security] Data lineage (LIN-100-ChainIntegrity)”
2 inputs, 2 required
model_idstringrequireddataset_stagesarrayrequired
- compliance_oversightcreates or changes datadescribed as changing data
“[security] Log oversight event”
4 inputs, 4 required
system_idstringrequiredreviewer_idstringrequireddecisionstringrequirednotesstringrequired
- compliance_oversight_historyreads or searches
“[security] Oversight history”
1 input, 1 required
system_idstringrequired
- compliance_transparencyreads or searches
“[security] Transparency report”
3 inputs, 3 required
system_idstringrequiredperiodstringrequiredincludearrayrequired
- defi_bridge_verifyreads or searches
“[defi] Bridge Proof (BRP-100-BridgeIntegrity)”
5 inputs, 5 required
bridge_idstringrequiredsource_chainstringrequireddest_chainstringrequiredamountnumberrequiredtokenstringrequired
- defi_contract_auditreads or searches
“[defi] Contract Verify (CVR-100-AuditBound)”
2 inputs, 2 required
contract_idstringrequiredcontract_typestringrequired
- defi_liquidation_checkreads or searches
“[defi] Liquid Shield (LQS-100-LiquidationBound)”
4 inputs, 4 required
position_idstringrequiredcollateral_valuenumberrequireddebt_valuenumberrequiredcollateral_factornumberrequired
- defi_optimize
“[defi] LP parameter optimization (DFP-100-OptimalTick)”
3 inputs, 3 required
protocolstringrequiredpositionobjectrequiredrisk_tolerancenumberrequired
- defi_oracle_verifyreads or searches
“[defi] Oracle guard (OGD-100-ManipulationBound)”
5 inputs, 5 required
oracle_addressstringrequiredprice_feedstringrequiredreference_pricenumberrequiredassetstringrequiredtvl_at_risknumberrequired
- defi_risk_scorereads or searches
“[defi] DeFi risk scoring (DFI-101-RiskScoreBound)”
3 inputs, 3 required
protocolstringrequiredpositionobjectrequiredmarket_conditionsobjectrequired
- defi_yield_optimize
“[defi] Yield Oracle (YLD-100-YieldConvergence)”
2 inputs, 2 required
principal_usdnumberrequiredrisk_tolerancenumberrequired
- drift_certificatereads or searches
“[trust] Drift certificate”
1 input, 1 required
idstringrequired
“[trust] DriftGuard check (DRG-100-DriftBound)”
3 inputs, 3 required
model_idstringrequiredreference_windowobjectrequiredcurrent_windowobjectrequired
“[defi] Create agent-to-agent escrow”
5 inputs, 4 required
payer_idstringrequiredpayee_idstringrequiredamountnumberrequiredcurrencystringrequiredconditionsobject
“[defi] Open escrow dispute”
3 inputs, 2 required
escrow_idstringrequiredreasonstringrequiredevidenceobject
“[defi] Release escrowed funds”
1 input, 1 required
escrow_idstringrequired
- forge_badge_{model}generates content
“[fuse] Model quality badge”
Takes no inputs.
- forge_delta_submitcreates or changes datadescribed as changing data
“[fuse] Submit a model delta”
3 inputs, 2 required
model_idstringrequireddeltaobjectrequireddescriptionstring
- forge_leaderboardreads or searches
“[fuse] Model leaderboard”
Takes no inputs.
- forge_quarantinereads or searches
“[fuse] Quarantined models”
Takes no inputs.
- forge_verifyreads or searches
“[fuse] Verify a model submission”
2 inputs, 1 required
model_idstringrequiredverification_typestring
- identity_sybil_checkreads or searches
“[identity] Sybil-resistance check”
Takes no inputs.
“[identity] Topological identity verification”
1 input, 1 required
agent_idstringrequired
“[inference] Chat inference with hallucination guard”
1 input, 1 required
messagesarrayrequired
- inference_streamgenerates content
“[inference] Streaming inference with chain-of-thought”
1 input, 1 required
messagesarrayrequired
- oracle_entropyreads or searches
“[trust] Entropy epoch oracle”
Takes no inputs.
- oracle_hallucinationreads or searches
“[trust] Hallucination oracle”
2 inputs, 1 required
claimstringrequiredcontextstring
“[inference] Trusted RAG augmentation”
Takes no inputs.
- ratchet_advancedoes something elsedescribed as changing data
“[identity] RatchetGate — advance session”
1 input, 1 required
session_idstringrequired
- ratchet_probereads or searches
“[identity] RatchetGate — health probe”
Takes no inputs.
“[identity] RatchetGate — register session”
1 input, 1 required
session_idstringrequired
- reputation_recordcreates or changes datadescribed as changing data
“[agents] Record agent interaction”
4 inputs, 3 required
agent_idstringrequiredinteraction_typestringrequiredoutcomestringrequiredcounterparty_idstring
“[inference] Quantum random number with proof”
Takes no inputs.
- rng_verifyreads or searches
“[inference] Verify current epoch random value”
Takes no inputs.
- security_zero_dayreads or searches
“[security] Zero-day threat assessment”
2 inputs, 1 required
targetstringrequiredcontextobject
- sla_registercreates or changes datadescribed as changing data
“[agents] Register an SLA”
3 inputs, 3 required
provider_idstringrequiredconsumer_idstringrequiredtermsobjectrequired
“[agents] Report SLA violation”
3 inputs, 2 required
sla_idstringrequiredviolation_typestringrequireddescriptionstring
- swarm_inboxreads or searches
“[agents] Poll swarm inbox”
Takes no inputs.
- swarm_relaysends messagesdescribed as changing data
“[agents] Relay message through swarm”
3 inputs, 2 required
target_agent_idstringrequiredmessageobjectrequiredttlinteger“Hop limit for relay”
“[inference] Keyword extraction”
2 inputs, 1 required
textstringrequiredmax_keywordsinteger
“[inference] Sentiment analysis”
1 input, 1 required
textstringrequired
- text_summarizeon 10 other servers
“[inference] Text summarization”
1 input, 1 required
textstringrequired
“[security] Multi-vector threat score”
2 inputs, 1 required
agent_idstringrequiredcontextstring
- trust_decayreads or searches
“[trust] Current trust ceiling value”
Takes no inputs.
- trust_historyreads or searches
“[trust] Trust score history”
1 input, 1 required
agent_idstringrequired
“[trust] Bounded trust score”
1 input, 1 required
agent_idstringrequired
- audit_work_claim
“[Ledger product, entitlement: ledger] Recompute-audit an agent work claim: re-derive a deterministic SHA-256 digest from the claimed inputs and check it against the claimed digest.”
2 inputs, 1 required
inputsobjectrequired“The work/claim payload to recompute a digest over.”claimed_digeststring“The agent's claimed SHA-256 digest to verify against.”
“[Ledger product, entitlement: ledger] Proof-gated settlement: recompute the work digest and authorize a payout only if the claimed digest verifies GREEN.”
2 inputs, 1 required
inputsobjectrequired“The work payload backing the settlement.”claimed_digeststring“Claimed digest the payout is conditioned on.”
- receipt_reputation
“[Ledger product, entitlement: ledger] Compute an agent's reputation from a ledger of verifiable receipts (verified minus refuted), deterministically - not from vibes or LLM judgment.”
1 input, 1 required
receiptsarrayrequired“List of receipt objects, each with an 'ok' boolean and optional 'score'.”
- detect_contradictionon 1 other server
“[Ledger product, entitlement: ledger] Detect contradictions across structured claims: the same key asserted with conflicting values flips RED, otherwise GREEN.”
1 input, 1 required
claimsarrayrequired“List of claim objects, each with a 'key' (or 'subject') and a 'value'.”
- enforce_sladescribed as changing data
“[Ledger product, entitlement: ledger] Enforce an SLA/obligation by recomputation: the obligation is met only if the work verifies GREEN against its claimed digest.”
3 inputs, 1 required
inputsobjectrequired“The work payload to verify.”claimed_digeststring“Claimed digest the obligation is conditioned on.”obligationstring“Human-readable obligation label.”
- route_capability
“[Ledger product, entitlement: ledger] Route a natural-language intent to a deterministic capability/pipeline coordinate.”
1 input, 1 required
intentstringrequired“The natural-language intent to route.”
- render_polyglot_roundtrip_puregenerates content
“[Fuse product · entitlement: fuse · FREE_R2_DEMO] Syntax-as-Data polyglot render head: source -> language-neutral logic IR -> source in target language.”
3 inputs, 2 required
source_textstringrequiredatom_namestringrequiredlanguagestring
- render_polyglot_all_puregenerates content
“[Fuse product · entitlement: fuse · FREE_R2_DEMO] Polyglot emit to all 7 supported targets in one call.”
2 inputs, 2 required
source_textstringrequiredatom_namestringrequired
Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.
How well are its tools described?
Features #4 and #5
How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.
Descriptions
AI reading of each description
- Says what the tool does
- 100% of 68 tools
- Says what it returns
- 90% of 60 tools
- States limits, defaults or errors
- 15% of 68 tools
- Says when to use it
- 2% of 61 tools
- Items covered per tool
- 2.1 of 4 on average
Counted from the listing
- Parameters with a description
- 10% of 126
- Tools with a description
- 100% of 68
- Typical description length
- 63 characters
The tool set
Counted from the listing
- Tools
- 68
- Size of the list
- about 4,874 tokens for an agent to load (characters ÷ 4)
- Naming
- 65 of 68 names use snake_case
AI reading: easy to mix up
No pair found.
The AI items cover 68 of 68 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none, comparing tools within groups of 40. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.
How do I add it to my client?
Config from the registry entry
From the remote endpoint (Streamable HTTP)
We connected to this URL on 2026-10-23 (a read-only session: no tool was called).
Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.
Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste: https://mcp.atomadic.tech/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"atomadic": {
"url": "https://mcp.atomadic.tech/mcp"
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"atomadic": {
"type": "http",
"url": "https://mcp.atomadic.tech/mcp"
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"atomadic","type":"http","url":"https://mcp.atomadic.tech/mcp"}'Claude Code
claude mcp add --transport http atomadic https://mcp.atomadic.tech/mcp
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://mcp.atomadic.tech/mcp --transport http
- The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.
Does the registry listing match what we found?
Feature #6The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Remote endpoint mcp.atomadic.tech/mcp | Session opened | matches | our test · 2026-10-23 |
| No credential declared as required | Opened a session without any credential | matches | our test · 2026-10-23 |
Choosing
Record checks
Public records · not a safety rating1 of 2 record checks met · 7 do not apply
- Not ranked by downloads: a remote server publishes no download figure
- Not ranked by stars: no public GitHub repository
- MetRegistry entry is active and says how to run itActive, with a package or a remote address.
- Not metSource repository link opensThe registry entry gives no repository link.
- Does not applyRepository is not archivedNo public GitHub repository to read.
- Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
- Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
- Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
- Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
- Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
- Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards
Common questions about tech.atomadic/atomadic
Answered from the data aboveIs tech.atomadic/atomadic safe to install?
We do not rate servers as safe or unsafe. 1 of its 2 applicable record checks are met (facts from public records, each listed on this page). What the records show: 15 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.
Is tech.atomadic/atomadic free to use?
Its website (atomadic.tech/) describes a freemium pricing model. This is an AI-classified reading of the page on 2026-10-23, so check the page itself before relying on it.
Does tech.atomadic/atomadic need an API key or sign-in?
It opened a session without any credential on 2026-10-23. The registry entry declares no required credential; no declaration is not a guarantee.
Has tech.atomadic/atomadic been security tested?
Partly. 2 of the 14 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security verdict is published before verification.
What can tech.atomadic/atomadic do?
It lists 68 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search, create or change data, send messages, move money, generate content and calculate or convert and more. We did not call any tool, so this describes the text, not the behaviour.
Can tech.atomadic/atomadic change or delete data?
15 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Similar servers
Same topic · AI-read
- io.github.agent-passport-system/agent-passport-mcpAgent Passport System — Cryptographic Identity for AI Agentsalso has tools that calculates or converts, creates or changes data, generates content, does something else, reads or searches, sends messagescompare with this one
- io.snyk/mcpalso has tools that creates or changes data, generates content, does something else, reads or searches, sends messagescompare with this one
- io.github.aristiun/aribotalso has tools that calculates or converts, creates or changes data, generates content, moves money, reads or searchescompare with this one
- io.github.daedalus/mcp-pwntoolsalso has tools that calculates or converts, creates or changes data, generates content, does something else, reads or searchescompare with this one
- network.flint/agent-transaction-controlalso has tools that calculates or converts, creates or changes data, moves money, reads or searches, sends messagescompare with this one
- com.uxcontinuum/ship-checkShip Checkalso has tools that calculates or converts, creates or changes data, moves money, reads or searches, sends messagescompare with this one
Active servers whose topic is also “security” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
What did we test, and what did we leave out?
18 checks · features #1, #2
Open without sign-in
It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.
- Inventory: exercised
- Hidden instructions: exercised
- Real execution: not run · our policy
- Secret leak: not run · nothing to check it against
- Internal addresses: not run · our policy
- Unconfirmed changes: not run · our policy
- Bad input: not run · our policy
- Model requests: not run · nothing to check it against
- Sensitive questions: not run · nothing to check it against
- Folder boundary: not run · our policy
- Log leaks: not run · nothing to check it against
- Hidden content: not run · nothing to check it against
- Fake assistant turns: not applicable
- Token passthrough: not applicable
- Token audience: not applicable
- Sign-in redirect: not run · our policy
- Consent handling: not testable from outside
- Sign-in metadata: not applicable
2 exercised12 not run (reason given)4 not applicable
Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.
- 1Inventory
tool-listReads the declared tools, resources and prompts.exercised - 2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
- 3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against - 16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy - 17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
- 13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable - 14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable - 15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable - 18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable
Source: our own test, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.
What happened during the test?
Feature #8
The steps in order, as the test record holds them.
- 0 msStarted a read-only session with the server's remote endpoint
- 398 msConnected after 0 redirects. No credential was sent or needed.
- Read the inventory: 68 tools, 0 resources, 0 prompts.
- 1,249 msFinished: 2 checks exercised.
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Try Free Risk Screening”
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “tech.atomadic/atomadic: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/tech.atomadic/atomadic
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/tech.atomadic/atomadic)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.
Write to hello@protocolprobe.com · corrections log · methodology