Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

RealMarket E-Signature Cost

REMOTE · TOOLS.REALMARKETLABS.COM

Compare e-signature costs per document and per year in Brazil (BRL) across providers.

68 Trust /100

Last scanned (19 hours ago)

Scores higher than 53% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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 Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability58
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 299 tokens (~299/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
  • Stability observed for 1 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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 5 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 4 Nov 26 68

    First indexed and scored.

Diagnostics

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 5 Nov 2026 · Probed https://tools.realmarketlabs.com/mcp/esign-cost

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=tools.realmarketlabs.com CN=YR2,O=Let's Encrypt,C=US 8 Sept 2026 7 Dec 2026 RSA 2048 SHA256-RSA 5d0b6502880ece5d7dc706ed3e12ac70df1
SANs: tools.realmarketlabs.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of tools.realmarketlabs.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
realmarketlabs.com. No DS 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://tools.realmarketlabs.com/mcp/esign-cost Verified 200
http (plaintext) http://tools.realmarketlabs.com/mcp/esign-cost HTTPS enforced 301 https://tools.realmarketlabs.com/mcp/esign-cost
MCP tools · 1 exposed · ~200 tokens

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 →

Tool Tokens
compare_esignature_costs ~200

Calculates the current cost per signed document and per year, and compares it with the public prices of other e-signature providers for the same volume, in Brazilian reais. Also notes per-user licensing and the contract renewal window.

NameTypeReqDescription
confirm_unusual_costboolean–Set true only after the user confirms a cost per document that the tool flagged as unusually high.
contract_renewalstringyesWhen the current contract renews.
current_providerstringyesE-signature tool used today; 'none' if not using one yet.
documents_per_monthintegeryesDocuments sent per month.
monthly_cost_brlnumberyesWhat the company pays per month today, in BRL (0 if none).
sendersintegeryesPeople who send documents for signature.
who_sendsstringyesWho sends: people on the team, an integrated system (API), or both.

No output schema declared.

No examples provided.

Install

How do I install the RealMarket E-Signature Cost MCP server?

RealMarket E-Signature Cost is a hosted endpoint at https://tools.realmarketlabs.com/mcp/esign-cost, 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 · tools.realmarketlabs.com

# add to Claude Code
claude mcp add --transport http com-realmarketlabs-tools-esign-cost 'https://tools.realmarketlabs.com/mcp/esign-cost'
Common questions

What is the RealMarket E-Signature Cost MCP server?

RealMarket E-Signature Cost is an MCP server listed in the public MCP registry as com.realmarketlabs.tools/esign-cost. Compare e-signature costs per document and per year in Brazil (BRL) across providers. This page covers its hosted endpoint (https://tools.realmarketlabs.com/mcp/esign-cost).

Is the RealMarket E-Signature Cost MCP server safe to use?

RealMarket E-Signature Cost scores 68 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 RealMarket E-Signature Cost MCP server expose?

RealMarket E-Signature Cost exposes 1 tool: compare_esignature_costs. Their descriptions and schemas cost roughly 200 tokens of context every time the server is loaded.

Does the RealMarket E-Signature Cost MCP server require authentication?

No. We connected to RealMarket E-Signature Cost without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the RealMarket E-Signature Cost MCP server still maintained?

RealMarket E-Signature Cost is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the RealMarket E-Signature Cost MCP server?

VerifyMCP ran 13 checks on RealMarket E-Signature Cost, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.