Kerne MCP server
io.github.kerne-protocol/honesty-indexkerne-protocolstreamable-httpv2.0.0Scanned
Read-only Kerne data on Base: signed reserves, signed stock quote, quote checks, vault state.
4 tools: 1 change things and 3 only read.
- Reads private data · 1
- Reads text others write · 4
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- 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 Kerne MCP server can do
The Kerne MCP server is published by the GitHub account kerne-protocol. It has 4 tools. It can create or change data (1 tool: verify_stock_quote), but cannot delete data. 3 tools only read.
1 tool reads private data (get_vault_state); 4 tools bring in text other people can write (get_signed_reserves, get_stock_quote, verify_stock_quote and 1 more).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 14, 2026, version 2.0.0.
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.
4 tools
Changes things 1Claude Code: ask
verify_stock_quoteChecks a Kerne stock quote: that the hash matches the signed string, that both signatures (EIP-191 over the document, EIP-712 over the on-chain Quote struct) recover to the publish…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 Checks a Kerne stock quote: that the hash matches the signed string, that both signatures (EIP-191 over the document, EIP-712 over the on-chain Quote struct) recover to the published quote signer, whether the quote has expired, and whether the price round it is bound to is still the latest round on the feed. Call it with no arguments to check the latest quote, or pass the three fields of a quote you were given by someone else. It checks who signed and whether the quote is still current. It does not judge whether the price is a good one.
Annotations the server declares
- title: Check a signed stock quote
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Only reads 3Show 3 read-only tools
get_signed_reservesThe latest signed proof of reserves for kUSD, the Kerne stablecoin on Base: outstanding kUSD, the USDC held in each PSM contract, the solvency ratio, skUSD share price and the hedg…Reads text others writeNo findings
Why it is in this group
- The name "get_signed_reserves" says "get": 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 The latest signed proof of reserves for kUSD, the Kerne stablecoin on Base: outstanding kUSD, the USDC held in each PSM contract, the solvency ratio, skUSD share price and the hedge account, all read on chain at one pinned block and signed every 15 minutes by a dedicated key that holds no funds. The hash and the signer are checked here before the result is returned, and the result says whether they checked. Set include_signed_bytes to true to get the exact signed string so you can check it yourself.
Annotations the server declares
- title: Signed proof of reserves for kUSD
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
get_stock_quoteThe latest signed REFERENCE quote for a one week covered call on TSLAc (Coinbase tokenized Tesla stock on Base): spot from the Chainlink feed, realized volatility, strike near 20 d…Reads text others writeNo findings
Why it is in this group
- The name "get_stock_quote" says "get": 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 The latest signed REFERENCE quote for a one week covered call on TSLAc (Coinbase tokenized Tesla stock on Base): spot from the Chainlink feed, realized volatility, strike near 20 delta, premium in basis points, expiry, and how long the quote is valid. A pricing agent signs a new one every 15 minutes. It is a reference price only: not an offer, not advice, not for US persons, and nothing executes from it. The result says whether the signatures checked and whether the quote has expired.
Annotations the server declares
- title: Signed reference quote for a covered call on TSLAc
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
get_vault_stateThe current on-chain state of the Kerne covered call vault for TSLAc on Base, read live in one call pinned to one block: epoch number, whether an epoch is live, whether sales are p…Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_vault_state" says "get": a word for reading.
What it can reach
- private-dataThe name "get_vault_state" says "get" and "vault": it reads secrets.
- private-dataThe description's first sentence says "vault": it reads secrets.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it The current on-chain state of the Kerne covered call vault for TSLAc on Base, read live in one call pinned to one block: epoch number, whether an epoch is live, whether sales are paused, deposit cap, total assets, the limits the vault enforces on any call it writes, the keeper, and the latest price round on its feed. It also lists what currently stops an epoch from opening. The vault is unaudited and its deposit cap is set by its owner; read deposits_open before assuming anyone can deposit.
Annotations the server declares
- title: Live state of the covered call vault
- 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 write4
- 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:06 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
- 1
- 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 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://kerne.fi/api/mcp: tools/list returned 4 tools to an anonymous client, including verify_stock_quote (write)
Posture changes
- Nov 20, 2026
- HTTP status of an anonymous initialize: 503 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 1
- Protocol version: none to 2025-06-18
- Nov 13, 2026
- HTTP status of an anonymous initialize: 200 to 503
- tools/list served without credentials: yes to no
- Protocol version: 2025-06-18 to none
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. HTTP status of an anonymous initialize: 503 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 1 (and 1 more).View diff
- HTTP status of an anonymous initialize: 503 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 1
- Protocol version: none to 2025-06-18
Tools4 added, 6 removed.+4 added−6 removedView diff
- Added:get_signed_reservesOnly reads
- Added:get_stock_quoteOnly reads
- Added:get_vault_stateOnly reads
- Added:verify_stock_quoteChanges things
- Removed:get_board
- Removed:get_corrections
- Removed:get_methodology
- Removed:get_right_of_reply
- Removed:get_row
- Removed:list_rows
PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 503; tools/list served without credentials: yes -> no; Protocol version: 2025-06-18 -> none.View diff
- HTTP status of an anonymous initialize: 200 to 503
- tools/list served without credentials: yes to no
- Protocol version: 2025-06-18 to none
Install
Pinned to version 2.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http honesty-index https://kerne.fi/api/mcpclaude mcp add --transport http honesty-index https://kerne.fi/api/mcpRun 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__honesty-index__get_signed_reserves",
"mcp__honesty-index__get_stock_quote",
"mcp__honesty-index__get_vault_state"
],
"ask": [
"mcp__honesty-index__verify_stock_quote"
],
"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 honesty-index. Review it before you use it.
Capability tags behind 4 rules
- mcp__honesty-index__get_signed_reserves untrusted-input
- mcp__honesty-index__get_stock_quote untrusted-input
- mcp__honesty-index__verify_stock_quote untrusted-input
- mcp__honesty-index__get_vault_state private-data, 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/io.github.kerne-protocol/honesty-index/verify?hash=5a15d948326a8e13768dcb9464a510fd1e5d0410c2164659f2d4f55d7ac3cd56" | jq -e '.changed == false'Pinned hash 5a15d948326a, from Nov 14, 2026, 21:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.kerne-protocol/honesty-index/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.kerne-protocol/honesty-index)Source: MCP Registry · repository. Synced Nov 14, 2026, 21:17 UTC.
Kerne MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Kerne MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 1 of which can change, send or delete something, and 0 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 Kerne MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Kerne 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 Kerne MCP server have?
- 4 tools: 1 write, 3 read. verify_stock_quote, get_signed_reserves, get_stock_quote and get_vault_state.
Does the Kerne MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Kerne MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Kerne MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 14, 2026. Every change is on this page and in its Atom feed.