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.

SSCMFI Bond Calculations

REMOTE · API.SSCMFI.COM

Industry-standard bond math for AI agents: price, yield, accrued interest, duration, yield-to-worst

Available components

0 this week 81 Trust /100

Last scanned (38 minutes ago)

Scores higher than 79% of remote servers

Reachable. Last reached 22 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 Security80
  • 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, and every tool looks verifiably read-only (it declares readOnlyHint: true, starts its name with a read verb and describes no write), so an anonymous caller can read but cannot change anything. We can't see whether a tool returns data specific to one caller, so keep any per-user data behind authorisation. View diagnostics → Pass
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • 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 Usability59
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 305 tokens (~305/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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

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

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

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.

  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 +6
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Nov 26 −4
    • HTTPS: pass → unverified ▼ security
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 0
    • Stability: 0.97 → pass security
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 29 Aug 26 0
    • Stability: unverified → 0.03 ▲ functional
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 22 Nov 2026 · Probed https://api.sscmfi.com/api/sscmfiMCPAPI

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.sscmfi.com CN=YE2,O=Let's Encrypt,C=US 4 Nov 2026 2 Feb 2027 ECDSA 256 ECDSA-SHA384 6fc633b09a3128d65e10cd00ec9e682928e
SANs: api.sscmfi.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.sscmfi.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
sscmfi.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://api.sscmfi.com/api/sscmfiMCPAPI Verified 200
http (plaintext) http://api.sscmfi.com/api/sscmfiMCPAPI Inconclusive 405
MCP tools · 1 exposed · ~305 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
calculate_bond_periodic ~305

Calculate price, yield, and accrued interest for Periodic bonds. Powered by the Standard Securities Calculation Methods - Fixed Income (https://api.sscmfi.com).

NameTypeReqDescription
callSchedulearray–Optional. List of discrete call dates and prices. AI Hint: The engine will automatically calculate the Yield-to-Worst using this schedule.
couponRatenumberyesAnnual coupon rate as a percentage (e.g., 5.0 for 5%). Use 0 for zero coupon bonds.
givenTypestringyesAre you providing the clean Price or the Yield to find the other?
givenValuenumberyesThe numeric value of the Price (e.g. 98.75) or Yield (as a percent e.g. 4.25).
maturityDatestringyesThe date the principal is due. Required format: MM/DD/YYYY (e.g., 01/05/2030). AI: Must use leading zeros and 4-digit years. (Ensure this is in the future relative to settlement).
securityTypestringyesCrucial for math accuracy. Treasury: Usually uses Actual/Actual. Corporate/Agency/Municipal: Usually uses 30/360. CD: Usually uses Actual/360.
settlementDatestring–Optional. Defaults to today. The date the money actually changes hands. Required format: MM/DD/YYYY (e.g., 07/04/2025).

No output schema declared.

No examples provided.

Install

How do I install the SSCMFI Bond Calculations MCP server?

SSCMFI Bond Calculations is a hosted endpoint at https://api.sscmfi.com/api/sscmfiMCPAPI, 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 · api.sscmfi.com

# add to Claude Code
claude mcp add --transport http com-sscmfi-bond 'https://api.sscmfi.com/api/sscmfiMCPAPI'
Common questions

What is the SSCMFI Bond Calculations MCP server?

SSCMFI Bond Calculations is an MCP server listed in the public MCP registry as com.sscmfi/bond. Industry-standard bond math for AI agents: price, yield, accrued interest, duration, yield-to-worst. This page covers its hosted endpoint (https://api.sscmfi.com/api/sscmfiMCPAPI).

Is the SSCMFI Bond Calculations MCP server safe to use?

SSCMFI Bond Calculations scores 81 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 SSCMFI Bond Calculations MCP server expose?

SSCMFI Bond Calculations exposes 1 tool: calculate_bond_periodic. Their descriptions and schemas cost roughly 305 tokens of context every time the server is loaded.

Does the SSCMFI Bond Calculations MCP server require authentication?

No. We connected to SSCMFI Bond Calculations without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the SSCMFI Bond Calculations MCP server still maintained?

SSCMFI Bond Calculations is still listed as active in the MCP registry. We last reached this channel on 22 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 SSCMFI Bond Calculations MCP server?

VerifyMCP ran 12 checks on SSCMFI Bond Calculations, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about SSCMFI Bond Calculations: HTTPS. 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.