Home / MCP registry index / com.moneteka/moneteka
MONETEKA
com.moneteka/moneteka in the official MCP registry.
Endpoint https://moneteka.com/api/mcp.
The registry describes it as: Ukrainian NBU coins and banknotes: catalogue facts, photos, reference prices, your collection.
We read its 24 tools on 2026-11-17. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again about every two weeks.
Connect it
The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:
claude mcp add --transport http moneteka https://moneteka.com/api/mcp{
"mcpServers": {
"moneteka": {
"url": "https://moneteka.com/api/mcp"
}
}
}code --add-mcp '{"name":"moneteka","type":"http","url":"https://moneteka.com/api/mcp"}'Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.
Let Claude Code check servers as it adds them
With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.
claude plugin marketplace add lazaretto-ai/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-pluginsTools it advertises
search_coins get_coin_details get_coin_prices get_catalog_entity compare_coins get_related_coins get_coin_links get_moneteka_profile get_my_collection get_collection_analytics get_account_capabilities prepare_moneteka_action add_collection_lot update_collection_lot remove_collection_lot get_my_wishlist add_wishlist_items remove_wishlist_item acquire_wishlist_coin get_my_support send_support_message get_sharing_settings manage_public_share render_moneteka_view
Tool changes
We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.
Fingerprint of its tools at our last full read (2026-11-17):
eaa0557df476308b. A client can hash the tools it is served the same way and compare;
the full value and a hash per tool are in this page as JSON.
Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.
Run this server? Show the check in your README
The badge reflects the latest read:
[](https://lazaretto.dev/mcp-registry/com-moneteka-moneteka)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. How tool poisoning works. What we found across the registry. Check another server.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.