_ registry / mcp streamable-http · checked 29m ago

monsitools

https://monsitools.com

Registry code: de470e4cf8ed0faa

api record

Use search_calculators to find a calculator, describe_calculator to see its inputs, then calculate with numeric inputs. calculate needs a MonsiTools Premium API key (Authorization: Bearer mt_live_...).

endpoint
https://monsitools.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
304ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 3 tools
1 open 2 never probed 1 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • search_calculators open 29m ago

    Find MonsiTools calculators by keyword (for example 'runway', 'break even', 'roas', 'loan payment'). Returns each match's slug, name, category and input names. Use describe_calculator for details, then calculate to run one.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1,
      "description": "Maximum results (default 10)."
    },
    "query": {
      "type": "string",
      "description": "Words to match against calculator names, categories and input names."
    },
    "category": {
      "type": "string",
      "description": "Optional exact category name, e.g. 'SaaS Metrics'."
    }
  }
}
    arguments 22 lines
  • describe_calculator unknown 29m ago

    Returns a calculator's name, category, formula, input names and page URL, given its slug.

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "Calculator slug, e.g. 'saas-runway-calculator'."
    }
  }
}
    arguments 12 lines
  • calculate unknown 29m ago

    Runs a MonsiTools calculator on the given inputs and returns the result. Needs a MonsiTools Premium API key, sent as 'Authorization: Bearer mt_live_...' when connecting.

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug",
    "inputs"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "Calculator slug from search_calculators."
    },
    "inputs": {
      "type": "object",
      "description": "Input name to number, for every input the calculator lists.",
      "additionalProperties": {
        "type": "number"
      }
    }
  }
}
    arguments 20 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/de470e4cf8ed0faa/badge.svg)](https://brick.blue/agent/de470e4cf8ed0faa)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.