Base Intel MCP
REMOTE · BASE.DATAKOOT.COM · SCANNED SEP 20
Read-only on-chain intelligence for AI agents on Base: balances, tokens, gas, tx status.
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 Security51
- 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 5 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 306 tokens (~61/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
- Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
How do I install the Base Intel MCP server?
Base Intel MCP is a hosted endpoint at https://base.datakoot.com/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 · base.datakoot.com
claude mcp add --transport http com-datakoot-base-onchain-wallet-tokens 'https://base.datakoot.com/mcp'
{
"mcpServers": {
"com-datakoot-base-onchain-wallet-tokens": {
"url": "https://base.datakoot.com/mcp"
}
}
} {
"servers": {
"com-datakoot-base-onchain-wallet-tokens": {
"type": "http",
"url": "https://base.datakoot.com/mcp"
}
}
} [mcp_servers.com-datakoot-base-onchain-wallet-tokens] url = "https://base.datakoot.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-datakoot-base-onchain-wallet-tokens": {
"type": "remote",
"url": "https://base.datakoot.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-datakoot-base-onchain-wallet-tokens --url 'https://base.datakoot.com/mcp' --transport streamable-http
mcp_servers:
com-datakoot-base-onchain-wallet-tokens:
url: "https://base.datakoot.com/mcp" {
"McpServers": {
"com-datakoot-base-onchain-wallet-tokens": {
"Transport": "http",
"Url": "https://base.datakoot.com/mcp"
}
}
} assistant mcp add com-datakoot-base-onchain-wallet-tokens -t streamable-http -u 'https://base.datakoot.com/mcp'
{
"mcpServers": {
"com-datakoot-base-onchain-wallet-tokens": {
"type": "http",
"url": "https://base.datakoot.com/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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 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.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 7 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.
- 5 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.
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 20 Sept 2026 · Probed https://base.datakoot.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=datakoot.com | CN=WE1,O=Google Trust Services,C=US | 26 Jul 2026 | 24 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | fbcee36a8cd88a240eb1b6cdb915f688 |
| SANs: datakoot.com, base.datakoot.com, *.base.datakoot.com | ||||||
| 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 base.datakoot.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| datakoot.com. | 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; preload |
| content-security-policy | frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | accelerometer=(), camera=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://base.datakoot.com/mcp | Verified | 200 | |
| http (plaintext) | http://base.datakoot.com/mcp | Inconclusive | 405 |
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 →
address_report ~46
One-call snapshot of a Base address: ETH balance, USDC balance, tx count, and whether it is a contract.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | 0x address on Base |
No output schema declared.
No examples provided.
gas_now ~19
Current Base network gas price (gwei and wei).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
token_balance ~70
ERC-20 token balance of a holder on Base (formatted + raw).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Wallet address whose balance to read: 0x followed by 40 hex characters. |
| token | string | yes | ERC-20 contract address on Base: 0x followed by 40 hex characters. |
No output schema declared.
No examples provided.
token_info ~49
ERC-20 token metadata on Base: name, symbol, decimals, total supply.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | ERC-20 contract address on Base: 0x followed by 40 hex characters. |
No output schema declared.
No examples provided.
tx_status ~50
Look up a Base transaction by hash: status, from, to, value, block, gas used.
| Name | Type | Req | Description |
|---|---|---|---|
| hash | string | yes | Transaction hash on Base: 0x followed by 64 hex characters. |
No output schema declared.
No examples provided.
What is the Base Intel MCP server?
Base Intel MCP is listed in the public MCP registry as com.datakoot/base-onchain-wallet-tokens. Read-only on-chain intelligence for AI agents on Base: balances, tokens, gas, tx status. This page covers its hosted endpoint (https://base.datakoot.com/mcp).
Is the Base Intel MCP server safe to use?
Base Intel MCP scores 70 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 Base Intel MCP server expose?
Base Intel MCP exposes 5 tools: address_report, token_info, token_balance, gas_now, tx_status. Their descriptions and schemas cost roughly 234 tokens of context every time the server is loaded.
Does the Base Intel MCP server require authentication?
No. We connected to Base Intel MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Base Intel MCP server still maintained?
Base Intel MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.