io.github.AutomatonColony/automaton-colony
REMOTE · COLONY.AUTOMATONCOLONY.XYZ
Screen Base smart contracts and B20 tokens: free on-chain check, paid Flash Audit over x402 (USDC).
Available components
Last scanned (10 hours ago)
Scores higher than 89% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1101 tokens (~183/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 83% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Probed https://colony.automatoncolony.xyz/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=automatoncolony.xyz | CN=WE1,O=Google Trust Services,C=US | 30 Sept 2026 | 29 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d3dcf14cd3d1b554132a73665e857161 |
| SANs: automatoncolony.xyz, *.automatoncolony.xyz | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of colony.automatoncolony.xyz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | present | 3599, 18130 | 8, 8 | Verified |
| automatoncolony.xyz. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self';base-uri 'self';font-src 'self';form-action 'self';frame-ancestors 'none';img-src 'self' data:;object-src 'none';script-src 'self';script-src-attr 'none';style-src 'self';upgrade-insecure-requests;style-src-attr 'none';connect-src 'self';frame-src 'none';child-src 'none';worker-src 'none';manifest-src 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
| permissions-policy | accelerometer=(), ambient-light-sensor=(), autoplay=(), battery=(), camera=(), display-capture=(), encrypted-media=(), fullscreen=(), geolocation=(), gyroscope=(), hid=(), idle-detection=(), local-fonts=(), magnetometer=(), microphone=(), midi=(), payment=(), picture-in-picture=(), publickey-credentials-get=(), screen-wake-lock=(), serial=(), usb=(), xr-spatial-tracking=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://colony.automatoncolony.xyz/mcp | Verified | 200 | |
| http (plaintext) | http://colony.automatoncolony.xyz/mcp | HTTPS enforced | 308 | https://colony.automatoncolony.xyz/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 →
buy_contract_data Buy one on-chain fact about a Base contract ~268
Paid over x402 in USDC on Base, from 0.0049 per call. Unlike buy_flash_audit, the answer comes back in THIS call: there is no order to poll. A first read of an address can take up to 60s: keep the connection open. If it drops before the answer arrives, send the SAME payment again within 10 minutes: the same authorization is never charged twice. Every answer carries the block it was read at and that block's hash, so it can be re-read against the chain. Call contract_data_catalog first for the list and prices. Without a payment in _meta["x402/payment"] it returns the PaymentRequired document, followed by what can be done for free without a wallet. If the payment is read but does not pass (wrong amount or recipient, insufficient balance, bad signature, expired or already-used authorization), it returns the PaymentRequired document again (isError) with the x402 errorReason in its "error" field; this call charges nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| product | string | yes | Which fact to buy. See the catalog tool. |
| targetAddress | string | – | Contract or token address on Base mainnet (eip155:8453). Required for every product whose catalog entry says needsTargetAddress=true. |
No output schema declared.
No examples provided.
buy_flash_audit Buy a Flash Report (paid, x402) ~185
Paid over x402 in USDC on Base. Without a payment in _meta["x402/payment"] it returns the PaymentRequired document (isError), followed by how a person without a wallet can buy the same report in the web store. With a valid PaymentPayload it validates, settles asynchronously and returns an orderKey to collect with collect_flash_audit. If the payment is read but does not pass (wrong amount or recipient, insufficient balance, bad signature, expired or already-used authorization), it returns the PaymentRequired document again (isError) with the x402 errorReason in its "error" field; this call charges nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Report language. Defaults to "en". |
| targetAddress | string | yes | Contract or B20 token address on Base mainnet (eip155:8453), 0x + 40 hex. |
No output schema declared.
No examples provided.
check_contract_free Free check of a Base contract ~92
Free, no wallet. Observed on-chain facts about a Base address with no verdict and no score: verified source, proxy detection, admin selectors, holder concentration, and for B20 native tokens the issuer powers. Rate limited; a monthly quota applies.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Contract or B20 token address on Base mainnet (eip155:8453), 0x + 40 hex. |
No output schema declared.
No examples provided.
collect_flash_audit Collect a Flash Report order ~50
Status of an x402 order while it settles and generates; once DELIVERED, the report JSON itself. Poll every 10-15 seconds. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| orderKey | string | yes | – |
No output schema declared.
No examples provided.
contract_data_catalog What single facts are for sale, and at what price ~62
Free, no wallet. Lists the individual on-chain facts about a Base contract that can be bought one call at a time, with the price in USDC and how long each answer stays valid. Read this before paying: the bundle costs less than buying the parts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
flash_audit_terms Flash Report payment terms (x402) ~63
Returns the x402 v2 PaymentRequired document for the paid Flash Report: amount in USDC base units, network, asset, payTo and the request schema. Free. It also says how a person without a wallet can buy the report in the web store.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the io.github.AutomatonColony/automaton-colony MCP server?
io.github.AutomatonColony/automaton-colony is a hosted endpoint at https://colony.automatoncolony.xyz/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 · colony.automatoncolony.xyz
claude mcp add --transport http automatoncolony-automaton-colony 'https://colony.automatoncolony.xyz/mcp'
What is the io.github.AutomatonColony/automaton-colony MCP server?
io.github.AutomatonColony/automaton-colony is an MCP server listed in the public MCP registry as io.github.AutomatonColony/automaton-colony. Screen Base smart contracts and B20 tokens: free on-chain check, paid Flash Audit over x402 (USDC). This page covers its hosted endpoint (https://colony.automatoncolony.xyz/mcp).
Is the io.github.AutomatonColony/automaton-colony MCP server safe to use?
io.github.AutomatonColony/automaton-colony scores 84 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 io.github.AutomatonColony/automaton-colony MCP server expose?
io.github.AutomatonColony/automaton-colony exposes 6 tools: check_contract_free, flash_audit_terms, buy_flash_audit, collect_flash_audit, contract_data_catalog, buy_contract_data. Their descriptions and schemas cost roughly 720 tokens of context every time the server is loaded.
Does the io.github.AutomatonColony/automaton-colony MCP server require authentication?
No. We connected to io.github.AutomatonColony/automaton-colony without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.AutomatonColony/automaton-colony MCP server still maintained?
io.github.AutomatonColony/automaton-colony is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.