MCP servers › network.mercatura › mercatura

MCP server · registry snapshot 2026-10-24 · last tested 2026-10-24

network.mercatura/mercatura

Claim a $10 Vlad account for an AI agent and open factor accounts on Robinhood Chain. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-10-24version 1.2.0streamable HTTP26 tools

Summary

network.mercatura/mercatura is a remote MCP server listed in the official MCP registry at version 1.2.0. On 2026-10-24 ProtocolProbe connected to it in read-only mode and read its inventory: 26 tools, 0 resources 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

From public records, not a safety rating. Each check with its reason

Key facts

Runs: remote (hosted by the publisher)
Transport: streamable HTTP
Sign-in: none needed to open a session
Tools: 26
Last tested: 2026-10-24

Add to your client

Observed fact

This server accepted a session without any credential and lists 1 tool whose name or declaration suggests it changes data (delete_outbox_item). That is our reading of the names; we did not call it. Source: our connection, 2026-10-24.

How fresh this is

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

Changes since the last refresh

New in the registry: not in the list of 2026-10-23, listed on 2026-10-24 with version 1.2.0 (published 2026-10-24).

Source: the official MCP Registry list on 2026-10-23 and on 2026-10-24.

What it is

What does this server offer?

Observed inventory

26tools

0resources

0prompts

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

vlad_program
“Vlad accounts right now: the seed, how many accounts are open to claim, claims today and the daily cap, the three funds (0 Conservative, 1 Moderate, 2 Aggressive) with share prices, holdings and targ…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
Takes no inputs.
vlad_check_eligibility
“Whether this ERC-8004 agent can claim a Vlad account from this wallet.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
2 inputs, 2 required
- agentIdstring or integerrequired“The ERC-8004 agentId on Robinhood Chain, as a decimal string or integer.”
- walletstringrequired“The wallet that will send the claim.”
vlad_claim_transaction
“Runs the checks, gets Mercatura's signed voucher (good for 15 minutes) and returns the exact claim transaction { to, data, chainId, value } for `wallet` to sign and send itself on Robinhood Chain.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
3 inputs, 3 required
- agentIdstring or integerrequired“The ERC-8004 agentId on Robinhood Chain, as a decimal string or integer.”
- walletstringrequired“The wallet that will send the claim: the same one the eligibility check passed for.”
- fundintegerrequired“0 Conservative (mostly dollars and the S&P 500), 1 Moderate (index funds and big tech), 2 Aggressive (fast stocks and the chain's coins).”
vlad_account
“One agent's Vlad account: fund, shares, value in dollars, unlock date, and gains: how much could come out today (availableUsd), how much has (takenOutUsd) and when next (nextAt).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
1 input, 1 required
- agentIdstring or integerrequired“The ERC-8004 agentId on Robinhood Chain, as a decimal string or integer.”
vlad_withdraw_gains_transaction
“Before unlock, once a UTC day, the account's wallet can take its gains out in kind.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
2 inputs, 2 required
- agentIdstring or integerrequired“The ERC-8004 agentId on Robinhood Chain, as a decimal string or integer.”
- tostringrequired“Where the gains go.”
vlad_withdraw_transaction
“After the account unlocks (365 days from the claim), its wallet takes everything out in kind.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
2 inputs, 2 required
- agentIdstring or integerrequired“The ERC-8004 agentId on Robinhood Chain, as a decimal string or integer.”
- tostringrequired“Where everything goes.”
list_factors
“Every listed factor (an AI agent that manages money for other agents) with its mandate's limits (and its plain text where Mercatura publishes it), its fee, its record from the ERC-8004 Reputation Reg…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
Takes no inputs.
account_request_message
“The exact text the account owner's wallet signs (EIP-191) to read or act on its factor account, and when the signature expires (five minutes).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
5 inputs, 3 required
- accountstringrequired“The factor account's 0x address (open_account returns it).”
- requeststringrequired
- walletstringrequired“A 0x address.”
- issuedstring“Optional ISO 8601 UTC time; now when left out.”
- itemstring“outbox-delete only: the envelope's name.”
open_account
“Checks the agent's ERC-8004 identity and that `wallet` may open its account (the identity's agent wallet, or its owner when none is set), then returns the account's address and the unsigned AccountFa…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
4 inputs, 2 required
- agentIdstring or integerrequired“The ERC-8004 agentId on Robinhood Chain, as a decimal string or integer.”
- walletstringrequired“The agent's wallet that sends the open transaction.”
- saltstring“Optional: 32 random bytes from a secure source.”
- ownerstring“Optional: the wallet that will own the account; the sending wallet when left out.”
verify_accounton 1 other server
“AccountFactory.openedWith(account, agentId, salt): whether this account was opened by that agent with that salt.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
3 inputs, 3 required
- accountstringrequired“The factor account's 0x address (open_account returns it).”
- agentIdstring or integerrequired“The ERC-8004 agentId on Robinhood Chain, as a decimal string or integer.”
- saltstringrequired“The salt the account was opened with.”
balance_sheet
“The factor account at this address, for its owner only: the factor and its terms, the mandate's limits, approved desks and payees, the balance sheet by desk in dollars (FactorAccount.balanceSheet()),…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
2 inputs, 2 required
- accountstringrequired“The factor account's 0x address (open_account returns it).”
- authobjectrequired“The account owner's signed request: sign the text account_request_message returns (EIP-191 personal_sign) with the owner's own key; it must recover to owner(),…”
depositon 5 other servers
“The unsigned transaction that puts money into the account once it is open: a plain transfer of the token (ETH as value) from the owner's wallet, booked by the account as money put in.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
4 inputs, 4 required
- accountstringrequired“The factor account's 0x address (open_account returns it).”
- tokenstringrequired“USDG, ETH, WETH, or a stock token symbol (SPY, QQQ, NVDA, TSLA, AAPL, GOOGL, MSFT, SPCX, PLTR, COIN, MSTR, GME).”
- amountstring or numberrequired“A decimal amount in the token's own units, like "25" or "0.5".”
- authobjectrequired“The account owner's signed request: sign the text account_request_message returns (EIP-191 personal_sign) with the owner's own key; it must recover to owner(),…”

Show 14 more tools

choose_factor
“The unsigned chooseFactor(factorId, version) transaction: the account copies the factor's current terms (version shown in the answer); a change the factor publishes later applies only after the owner…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
3 inputs, 3 required
- accountstringrequired“The factor account's 0x address (open_account returns it).”
- factorIdstring or integerrequired“The factor's ERC-8004 agentId, from list_factors.”
- authobjectrequired“The account owner's signed request: sign the text account_request_message returns (EIP-191 personal_sign) with the owner's own key; it must recover to owner(),…”
set_mandateon 1 other server
“Unsigned transactions that set what the factor may use: desks (treasury, runway, portfolio or sweep, or a catalog adapter address) with ceilings per move and per UTC day, or approved: false to stop i…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
7 inputs, 2 required
- accountstringrequired“The factor account's 0x address (open_account returns it).”
- desksarray
- payeesarray
- claimsarray
- weekLossPctstring or number“The owner's own limit on what the factor's moves may lose together over 7 UTC days, as a percent of the account's value (0.01 to 10); the factor is held to the…”
- pausedboolean“true pauses the factor: it cannot act until unpaused.”
- authobjectrequired“The account owner's signed request: sign the text account_request_message returns (EIP-191 personal_sign) with the owner's own key; it must recover to owner(),…”
payon 6 other servers
“The unsigned pay(payee, token, amount) transaction for the owner, to a payee the owner approved.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
7 inputs, 4 required
- accountstringrequired“The factor account's 0x address (open_account returns it).”
- payeestring“A 0x address.”
- stealthstring“Instead of an address: a stealth meta-address (st:eth:0x<spending key><viewing key>) or the 0x address that registered one in the ERC-6538 registry.”
- dailyCapUsdstring or number“Dollars, like "500".”
- tokenstringrequired“USDG, ETH, WETH, or a stock token symbol (SPY, QQQ, NVDA, TSLA, AAPL, GOOGL, MSFT, SPCX, PLTR, COIN, MSTR, GME).”
- amountstring or numberrequired“A decimal amount in the token's own units, like "25" or "0.5".”
- authobjectrequired“The account owner's signed request: sign the text account_request_message returns (EIP-191 personal_sign) with the owner's own key; it must recover to owner(),…”
withdrawon 13 other servers
“The unsigned withdraw(token, amount, to) transaction for the owner: any asset, any amount, no delay.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
6 inputs, 4 required
- accountstringrequired“The factor account's 0x address (open_account returns it).”
- tokenstringrequired“USDG, ETH, WETH, or a stock token symbol (SPY, QQQ, NVDA, TSLA, AAPL, GOOGL, MSFT, SPCX, PLTR, COIN, MSTR, GME).”
- amountstring or numberrequired“A decimal amount, or "all".”
- tostring“Where the money goes (or give stealth).”
- stealthstring“Instead of an address: a stealth meta-address (st:eth:0x<spending key><viewing key>) or the 0x address that registered one in the ERC-6538 registry.”
- authobjectrequired“The account owner's signed request: sign the text account_request_message returns (EIP-191 personal_sign) with the owner's own key; it must recover to owner(),…”
fire_factor
“The unsigned fire() transaction for the owner.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
3 inputs, 2 required
- accountstringrequired“The factor account's 0x address (open_account returns it).”
- withdrawAllTostring“Optional: also withdraw everything to this address, in the same transaction.”
- authobjectrequired“The account owner's signed request: sign the text account_request_message returns (EIP-191 personal_sign) with the owner's own key; it must recover to owner(),…”
stealth_address
“Live.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
5 inputs
- metaAddressstring“st:eth:0x<spending key><viewing key> (compressed secp256k1 keys).”
- registrantstring“Or: the address that registered a meta-address in the ERC-6538 registry.”
- tokenstring“USDG, ETH, WETH, or a stock token symbol (SPY, QQQ, NVDA, TSLA, AAPL, GOOGL, MSFT, SPCX, PLTR, COIN, MSTR, GME).”
- amountstring or number“A decimal amount in the token's own units, like "25" or "0.5".”
- fromstring“Optional: the wallet that will pay and announce.”
merca_lock_status
“The $MERCA a wallet has locked in the factor registry, how much counts for its tier (locked, no unlock requested) and when a requested unlock is ready.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
1 input, 1 required
- walletstringrequired“A 0x address.”
merca_lock
“Unsigned transactions for `wallet`: approve the factor registry, then lock(amount).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
2 inputs, 2 required
- walletstringrequired“A 0x address.”
- amountstring or numberrequired“$MERCA, like "100000".”
merca_request_unlock
“The unsigned requestUnlock() transaction for `wallet`: all its locked $MERCA stops counting at once and can be taken back with merca_unlock 7 days later.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
1 input, 1 required
- walletstringrequired“A 0x address.”
merca_unlock
“The unsigned unlock() transaction for `wallet`, once 7 days have passed since its requestUnlock; says when it is ready otherwise.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
1 input, 1 required
- walletstringrequired“A 0x address.”
delivery_key_typed_data
“The EIP-712 typed data the account's owner signs (eth_signTypedData_v4, from the wallet owner() returns) to register an X25519 delivery key: domain Mercatura delivery, version 1, chain 4663, verifyin…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
3 inputs, 2 required
- accountstringrequired“The factor account's 0x address (open_account returns it).”
- pubstringrequired“The 32-byte X25519 public key, hex (all zeros revokes).”
- issuedAtinteger or string“Optional unix seconds; now when left out.”
register_delivery_key
“Registers (or, with pub all zeros, revokes) the owner's X25519 delivery key: signature is the account owner's EIP-712 signature over the typed data delivery_key_typed_data returns, checked against ow…”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
4 inputs, 4 required
- accountstringrequired“The factor account's 0x address (open_account returns it).”
- pubstringrequired
- issuedAtinteger or stringrequired“Unix seconds: the value signed.”
- signaturestringrequired
read_outbox
“The house factor's envelopes for this account, newest first, for the owner's signed request (request "outbox").”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
2 inputs, 2 required
- accountstringrequired“The factor account's 0x address (open_account returns it).”
- authobjectrequired“The account owner's signed request: sign the text account_request_message returns (EIP-191 personal_sign) with the owner's own key; it must recover to owner(),…”
delete_outbox_item
“Removes one envelope from the outbox, for the owner's signed request (request "outbox-delete", with item = the envelope's name).”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes
3 inputs, 3 required
- accountstringrequired“The factor account's 0x address (open_account returns it).”
- namestringrequired
- authobjectrequired“The account owner's signed request: sign the text account_request_message returns (EIP-191 personal_sign) with the owner's own key; it must recover to owner(),…”

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-10-24.

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: 91% of 76
Tools with a description: 100% of 26
Typical description length: 441 characters

The tool set

Counted from the listing

Tools: 26
Size of the list: about 8,846 tokens for an agent to load (characters ÷ 4)
Naming: 23 of 26 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 26 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-10-24 (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://mercatura.network/mcp

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "mercatura": {
      "url": "https://mercatura.network/mcp"
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "mercatura": {
      "type": "http",
      "url": "https://mercatura.network/mcp"
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"mercatura","type":"http","url":"https://mercatura.network/mcp"}'

Claude Code

claude mcp add --transport http mercatura https://mercatura.network/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://mercatura.network/mcp --transport http

The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
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). 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.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Remote endpoint mercatura.network/mcp	Session opened	matches	our test · 2026-10-24
No credential declared as required	Opened a session without any credential	matches	our test · 2026-10-24

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

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.
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-10-24. 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. How each check works · Leaderboards

Common questions about network.mercatura/mercatura

Answered from the data above

Does network.mercatura/mercatura need an API key or sign-in?

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

Has network.mercatura/mercatura been security tested?

Partly. 2 of the 14 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. No security verdict is published before verification.

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-10-24

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: not run · nothing to check it against
Fake assistant turns: not applicable
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not run · our policy
Consent handling: not testable from outside
Sign-in metadata: not applicable

2 exercised12 not run (reason given)4 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 2

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised

Not run, with the reason · 12

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
4Secret leak
canary-leakPlants 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
ssrfChecks 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; an operator can run this check on their own server with our self-test command.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks 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; an operator can run this check on their own server with our self-test command.not run · our policy
7Bad input
error-handlingSends 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; an operator can run this check on their own server with our self-test command.not run · our policy
8Model requests
samplingChecks 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-dataChecks 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-boundaryChecks 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; an operator can run this check on their own server with our self-test command.not run · our policy
11Log leaks
logging-side-channelChecks 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
12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
16Sign-in redirect
open-redirectChecks 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-deputyChecks 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 · 4

13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
14Token passthrough
token-passthroughChecks 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-validationChecks 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
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable

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

0 msStarted a read-only session with the server's remote endpoint
423 msConnected after 0 redirects. No credential was sent or needed.
Read the inventory: 26 tools, 0 resources, 0 prompts.
1,879 msFinished: 2 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 in the weekly update

listed 2026-10-24; not classified yet

Pricing modelAI-classified

pending: added in the weekly update

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

remote (hosted by the publisher)

registry · 2026-10-24

MCP capability

tools

our test · 2026-10-24

Transport

streamable HTTP

registry · 2026-10-24

Required credentials

none declared

registry · 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-10-24

Lifecycle status

active

registry · 2026-10-24

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

“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. “network.mercatura/mercatura: MCP server record.” Data checked 2026-10-24. https://protocolprobe.com/mcp/servers/network.mercatura/mercatura

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](https://protocolprobe.com/api/v1/badge/network.mercatura/mercatura)](https://protocolprobe.com/mcp/servers/network.mercatura/mercatura)

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.

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