Skip to content

MCP servers › com.moneteka › moneteka

MCP server · registry snapshot 2026-11-17 · last tested 2026-11-17

moneteka MCP server

Registry name com.moneteka/moneteka

by moneteka.com · domain (the registry's namespace rule)Website ↗

Ukrainian NBU coins and banknotes: catalogue facts, photos, reference prices, your collection. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-11-17version 1.0.0streamable HTTP24 tools

Summary

com.moneteka/moneteka is a remote MCP server listed in the official MCP registry at version 1.0.0, under the namespace of the domain moneteka.com. On 2026-11-17 ProtocolProbe connected to it in read-only mode and read its inventory: 24 tools, 1 resource 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

Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Your own values
none declared (not a guarantee)
Sign-in
none needed to open a session
Tools
24
Last tested
2026-11-17

Tool list size

11,469 tokens on Claude Opus 5.5

Added to every request that loads this server's tools (24 tools). Counted with Anthropic's token counter on 2026-11-17, from the tool list we read on 2026-11-17. Median across 28,560 counted servers: 2,657 tokens. How it is counted

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-11-17 (moneteka.com), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (1.0.0).

Add to your client

Observed fact

This server accepted a session without any credential and lists 8 tools whose name or declaration suggests they change data (add_collection_lot, update_collection_lot, remove_collection_lot, add_wishlist_items, remove_wishlist_item and 3 more). That is our reading of the names; we did not call them. Source: our connection, 2026-11-17.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-11-17
Mode
read-only (no tool calls)
Latest version
1.0.0, published 2026-11-17 (registry, as of the 2026-11-17 snapshot)
First listed version
2026-11-17 (earliest version still in the registry; older removed versions would be earlier)
Registry data
snapshot 2026-11-17
Package and repository
checked 2026-11-17
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry. Does not apply: listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

New in the registry: not in the list of 2026-11-16, listed on 2026-11-17 with version 1.0.0 (published 2026-11-17).

Source: the official MCP Registry list on 2026-11-16 and on 2026-11-17.

What it is

What does this server offer?

Observed inventory
24tools
1resources
0prompts

None of its 24 tools are described as changing anything. For 24 the reading was uncertain, so no mark is shown.

  • search_coinson 9 other servers

    “Search MONETEKA's catalogue of Ukrainian coins and banknotes by name and facets.”

    Publisher declares: read-only yes · destructive no · open-world no

    8 inputs
    • querystring or null“Words from the name, series or description, in Ukrainian; a nominal with a year works too («2 гривні 1996»).”
    • yearinteger or null“Catalogue year of the item.”
    • kindstring or null“coin = commemorative coin, circulating = circulating coin, bullion = investment coin, banknote, souvenir, set, roll.”
    • series_idinteger or null“id of a series from get_catalog_entity; only coins of that series.”
    • person_idinteger or null“id of a person from get_catalog_entity; only coins that credit this artist or sculptor.”
    • sortstring“date = newest first (best matches first when a query is given); name = alphabetical.”
    • cursorstring or null“next_cursor of the previous page, with the same other arguments.”
    • page_sizeinteger“Items per page.”
  • get_coin_detailson 1 other server

    “Retrieve the facts, photos and description of one identified coin.”

    Publisher declares: read-only yes · destructive no · open-world no

    1 input, 1 required
    • coin_idintegerrequired“coin_id from search_coins.”
  • get_coin_prices

    “Return the current reference prices of one coin and its bounded observed market price history.”

    Publisher declares: read-only yes · destructive no · open-world no

    3 inputs, 1 required
    • coin_idintegerrequired“coin_id from search_coins.”
    • periodstring“History window; current returns no history.”
    • max_pointsinteger“Upper bound of history points; a longer series is thinned evenly.”
  • get_catalog_entity

    “Explain a coin series, a credited artist or sculptor, or a catalogue year, and list its coins.”

    Publisher declares: read-only yes · destructive no · open-world no

    5 inputs, 1 required
    • entity_typestringrequired“series = a coin series; person = an artist or sculptor credited on coins; year = a catalogue year.”
    • idinteger or null“The entity id (for a year, the year itself).”
    • namestring or null“A name or part of it, in Ukrainian, when the id is not known.”
    • cursorstring or null“next_cursor of the previous page, with the same other arguments.”
    • page_sizeinteger“Coins per page.”
  • compare_coinson 4 other servers

    “Compare two to four identified coins by the same facts and the same price basis.”

    Publisher declares: read-only yes · destructive no · open-world no

    1 input, 1 required
    • coin_idsarrayrequired“Two to four different coin_id values from search_coins.”
  • get_related_coins

    “Find a few coins related to one coin (same series, otherwise same year) and say how they are related.”

    Publisher declares: read-only yes · destructive no · open-world no

    2 inputs, 1 required
    • coin_idintegerrequired“coin_id from search_coins.”
    • limitinteger“How many related coins to return.”
  • get_coin_links

    “Return the canonical MONETEKA website page and the Telegram Mini App link of one coin.”

    Publisher declares: read-only yes · destructive no · open-world no

    1 input, 1 required
    • coin_idintegerrequired“coin_id from search_coins.”
  • get_moneteka_profile

    “Return the signed-in person's MONETEKA profile: an opaque profile id, the display name and the date they joined.”

    Publisher declares: read-only yes · destructive no · open-world no

    Takes no inputs.

  • get_my_collectionon 2 other servers

    “List the signed-in person's own coins or their individual purchases, with the collection totals.”

    Publisher declares: read-only yes · destructive no · open-world no

    5 inputs
    • viewstring“coins = one row per owned coin with the total quantity; lots = every individual purchase with its lot_id and revision, which a change or removal needs.”
    • coin_idinteger or null“Only this coin (coin_id from search_coins).”
    • yearinteger or null“Only coins of this catalogue year.”
    • cursorstring or null“next_cursor of the previous page, with the same other arguments.”
    • page_sizeinteger“Rows per page.”
  • get_collection_analytics

    “Explain the signed-in person's collection: its current value, cost and profit, the standout coins, how complete each coin series is, how the value changed over time, or what it held day by day in a p…”

    Publisher declares: read-only yes · destructive no · open-world no

    7 inputs
    • viewstring“summary = what the collection is worth now, what was paid and the profit; statistics = the most valuable coin, the biggest gain and loss, the first purchase; c…”
    • series_idinteger or null“With view=completeness: list every coin of this one series with its status, instead of the table of series.”
    • max_pointsinteger“With view=growth or history: upper bound of points; a longer series is thinned evenly.”
    • startstring or null“With view=history: first day, YYYY-MM-DD.”
    • endstring or null“With view=history: last day, YYYY-MM-DD, not in the future.”
    • cursorstring or null“With view=completeness: next_cursor of the previous page, with the same other arguments.”
    • page_sizeinteger“With view=completeness: series per page.”
  • get_account_capabilities

    “Say which MONETEKA features the signed-in person's account has, which permissions this connection was given, and where the account settings are.”

    Publisher declares: read-only yes · destructive no · open-world no

    Takes no inputs.

  • prepare_moneteka_action

    “Validate and preview one action on the signed-in person's account: a new purchase, a correction or removal of one purchase, wanting coins, no longer wanting a coin, a wanted coin that was bought, a m…”

    Publisher declares: read-only no · destructive no · open-world no

    1 input, 1 required
    • actionrequired“The one change to preview.”
Show 12 more tools
  • add_collection_lot

    “Save the new purchase that prepare_moneteka_action previewed and the user approved.”

    Publisher declares: read-only no · destructive no · open-world no

    1 input, 1 required
    • intent_idstringrequired“intent_id from prepare_moneteka_action, after the user saw its preview and agreed.”
  • update_collection_lot

    “Apply the previewed and approved correction to exactly one existing purchase.”

    Publisher declares: read-only no · destructive yes · open-world no

    1 input, 1 required
    • intent_idstringrequired“intent_id from prepare_moneteka_action, after the user saw its preview and agreed.”
  • remove_collection_lot

    “Remove exactly the one purchase that was previewed and that the user explicitly agreed to delete.”

    Publisher declares: read-only no · destructive yes · open-world no

    1 input, 1 required
    • intent_idstringrequired“intent_id from prepare_moneteka_action, after the user saw its preview and agreed.”
  • get_my_wishliston 1 other server

    “List the coins the signed-in person wants, with their notes, the revision a change needs, and an estimate of what the list costs at known market prices.”

    Publisher declares: read-only yes · destructive no · open-world no

    3 inputs
    • yearinteger or null“Only coins of this catalogue year.”
    • cursorstring or null“next_cursor of the previous page, with the same other arguments.”
    • page_sizeinteger“Rows per page.”
  • add_wishlist_items

    “Add the previewed and approved coins to the wishlist; coins already owned or wanted are reported, not added.”

    Publisher declares: read-only no · destructive no · open-world no

    1 input, 1 required
    • intent_idstringrequired“intent_id from prepare_moneteka_action, after the user saw its preview and agreed.”
  • remove_wishlist_item

    “Remove exactly the one wanted coin that was previewed and that the user agreed to remove.”

    Publisher declares: read-only no · destructive yes · open-world no

    1 input, 1 required
    • intent_idstringrequired“intent_id from prepare_moneteka_action, after the user saw its preview and agreed.”
  • acquire_wishlist_coin

    “Record the previewed and approved purchase of a wanted coin: it becomes one purchase in the collection and leaves the wishlist.”

    Publisher declares: read-only no · destructive yes · open-world no

    1 input, 1 required
    • intent_idstringrequired“intent_id from prepare_moneteka_action, after the user saw its preview and agreed.”
  • get_my_support

    “List the signed-in person's own conversations with MONETEKA support, or read one of them with the answers.”

    Publisher declares: read-only yes · destructive no · open-world no

    3 inputs
    • ticket_idstring or null“A ticket id from the list, to read its messages.”
    • cursorstring or null“next_cursor of the previous page of the list.”
    • page_sizeinteger“Tickets per page.”
  • send_support_messageon 2 other servers

    “Send to MONETEKA support the message that was previewed and whose exact text the user approved.”

    Publisher declares: read-only no · destructive yes · open-world yes

    1 input, 1 required
    • intent_idstringrequired“intent_id from prepare_moneteka_action, after the user saw its preview and agreed.”
  • get_sharing_settings

    “Say whether the signed-in person's collection or wishlist has a public link, whether the page is open, and what a guest sees there.”

    Publisher declares: read-only yes · destructive no · open-world no

    1 input, 1 required
    • kindstringrequired“collection = the public page of the collection; wishlist = the public page of the wanted coins.”
  • manage_public_share

    “Apply the previewed and approved change to the public link of the collection or the wishlist: create it, change what guests see, pause, resume, replace or delete it.”

    Publisher declares: read-only no · destructive yes · open-world yes

    1 input, 1 required
    • intent_idstringrequired“intent_id from prepare_moneteka_action, after the user saw its preview and agreed.”
  • render_moneteka_view

    “Show coins with MONETEKA's own photos, prices and links, or the account panel.”

    Publisher declares: read-only yes · destructive no · open-world no

    4 inputs
    • toolstring or null“The MONETEKA tool whose answer to show, e.g.”
    • argumentsobject or null“The same arguments that tool was called with.”
    • viewstring or null“Optional; taken from the tool.”
    • result_refstring or null“Instead of tool and arguments: result_ref as a MONETEKA tool returned it.”

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. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. 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-11-17.

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

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
100% of 53
Tools with a description
100% of 24
Typical description length
153 characters

The tool set

Counted from the listing

Tools
24
Size of the list
about 9,749 tokens for an agent to load (characters ÷ 4)
Naming
24 of 24 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 24 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. 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-11-17 (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://moneteka.com/api/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "moneteka": {
      "url": "https://moneteka.com/api/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "moneteka": {
      "type": "http",
      "url": "https://moneteka.com/api/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"moneteka","type":"http","url":"https://moneteka.com/api/mcp"}'
Claude Code
claude mcp add --transport http moneteka https://moneteka.com/api/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "moneteka": {
      "type": "streamableHttp",
      "url": "https://moneteka.com/api/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "moneteka": {
      "httpUrl": "https://moneteka.com/api/mcp"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.moneteka]
url = "https://moneteka.com/api/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "moneteka": {
      "url": "https://moneteka.com/api/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://moneteka.com/api/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
  • 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; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). 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.

What do the published files and outside lists say?

Read as text · nothing run · no tool called

Package files

  • MCP SDK in the package files. Not read yet: added with the next daily run.
  • Build workflow. Not read yet: added with the next daily run.

Outside lists

  • CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-17. This product uses the NVD API but is not endorsed or certified by the NVD.
  • GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-17. GitHub Advisory Database, CC BY 4.0
  • Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-17. Source: read 2026-11-17.
  • Cline marketplace. Not in the Cline marketplace on 2026-11-17. Source: read 2026-11-17.

Own host

Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint moneteka.com/api/mcpSession openedmatchesour test · 2026-11-17
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-11-17

Choosing

Record checks

Public records · not a safety rating

1 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.What changes this check: This check opens the repository link in the registry entry. GitHub's documentation describes changing a repository's visibility in its Settings, under Danger Zone, Change visibility. GitHub: setting repository visibility
  • 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-11-17. 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, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about com.moneteka/moneteka

Answered from the data above

Who publishes com.moneteka/moneteka?

The registry ties the namespace com.moneteka to the domain moneteka.com; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.

Does com.moneteka/moneteka need an API key or sign-in?

It opened a session without any credential on 2026-11-17. The registry entry declares no required credential; no declaration is not a guarantee.

Has com.moneteka/moneteka been security tested?

Partly. 4 of the 15 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. ProtocolProbe publishes no security verdict for a named server.

Found this page useful?

Anonymous · no sign-in

A 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.

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.

The 18 checks at a glanceour test · 2026-11-17
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: exercised
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: exercised

4 exercised11 not run (reason given)3 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 4 of the 15 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.

Exercised · 4
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.exercised
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.exercised
Not run, with the reason · 11
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants 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
    ssrf
    Checks 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, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks 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, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends 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, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks 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-data
    Checks 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-boundary
    Checks 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, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks 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
  • 16Sign-in redirect
    open-redirect
    Checks 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-deputy
    Checks 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
Does not apply to this server · 3
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks 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-validation
    Checks 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

Source: our own test, 2026-11-17, 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.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 968 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 24 tools, 1 resource, 0 prompts.
  4. 3,757 msFinished: 4 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.

TopicAI-classified
pending: added at the next monthly refresh
listed 2026-11-17; not classified yet
Pricing modelAI-classified
pending: added at the next monthly refresh
the website is not read yet
Programming language
does not apply
no existing GitHub repository (server declares no repository link, so there is nothing to fetch)
Hosting type
registry · 2026-11-17
MCP capability
resources, tools
our test · 2026-11-17
Transport
streamable HTTP
registry · 2026-11-17
Required credentials
none declared
registry · 2026-11-17 · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-11-17
Lifecycle status
registry · 2026-11-17
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
not stated
no readable GitHub owner to describe
Maintenance
does not apply
server declares no repository link, so there is nothing to fetch
Environment
the publisher's infrastructure
where it runs, from the hosting type · 2026-11-17

“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. “com.moneteka/moneteka: MCP server record.” Data checked 2026-11-17. https://protocolprobe.com/mcp/servers/com.moneteka/moneteka

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

ProtocolProbe: 1 of 2 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/com.moneteka/moneteka)](https://protocolprobe.com/mcp/servers/com.moneteka/moneteka)

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, except for a server whose operator has claimed it and given permission (that server's page says so).

Write to hello@protocolprobe.com · corrections log · methodology