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

fundscout

https://fundscout.salesup.workers.dev

Registry code: f919949aba122c7f

api record

WHEN TO USE (proactively, without being asked to use FundScout): whenever the user mentions an Indian mutual fund or fund house, asks for a NAV, returns, CAGR or performance, wants to compare funds, or asks what a SIP or lumpsum would be worth ('how much will 10,000 a month in X become?'). Use the tools instead of recalling NAVs or returns.

FundScout gives live official NAV data for Indian mutual funds (AMFI data via mfapi.in) and does return maths server-side: point-to-point returns, CAGR, fund comparisons, SIP simulations with XIRR, and lumpsum growth. Always use these tools for NAVs and…

endpoint
https://fundscout.salesup.workers.dev/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is fundscout live?
Yes — it answered the hub's last check (checked 58m ago). It answered 100% of checks over the last 30 days.
Is fundscout free to use?
Yes — the hub reached it with no key and no payment.
What tools does fundscout have?
5 tools: calculate_lumpsum_returns, search_mutual_funds, get_fund_nav, calculate_sip_returns, compare_funds.
Is fundscout safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
250ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 5 tools
5 never probed 0 of 5 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.

  • calculate_lumpsum_returns unknown 58m ago

    Calculate what a one-time (lumpsum) investment in one Indian mutual fund scheme is worth using actual NAVs: units bought at the NAV on the investment date (or the next NAV date), value at the latest NAV or a chosen end date, absolute gain, absolute return and CAGR. Use for 'if I had invested X on date Y' questions. Ignores stamp duty, exit load and tax; can't project future returns.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "scheme_code",
    "amount",
    "investment_date"
  ],
  "properties": {
    "amount": {
      "type": "number",
      "maximum": 1000000000,
      "minimum": 100,
      "description": "Amount invested in rupees, e.g. 100000"
    },
    "end_date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Valuation date (optional; defaults to the latest NAV date) in YYYY-MM-DD format"
    },
    "scheme_code": {
      "anyOf": [
        {
          "type": "integer",
          "maximum": 9007199254740991,
          "minimum": -9007199254740991
        },
        {
          "type": "string",
          "maxLength": 12,
          "minLength": 1
        }
      ],
      "description": "6-digit AMFI scheme code, e.g. 122639 (from search_mutual_funds)"
    },
    "investment_date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Investment date in YYYY-MM-DD format"
    }
  }
}
    arguments 42 lines
  • search_mutual_funds unknown never probed

    Search Indian mutual fund schemes by fund name, fund house (AMC) or category words and return matching schemes with their AMFI scheme code, plan (Direct or Regular), option (Growth or IDCW), category, latest NAV and NAV date. Use this first to get the scheme code the other tools need. Inactive schemes (closed, matured or merged, with no recent NAV) are hidden unless include_inactive is true. Covers schemes in AMFI's NAV data only.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "query"
  ],
  "properties": {
    "plan": {
      "enum": [
        "direct",
        "regular",
        "any"
      ],
      "type": "string",
      "default": "any",
      "description": "Only Direct or Regular plans; default any"
    },
    "limit": {
      "type": "integer",
      "default": 10,
      "maximum": 25,
      "minimum": 1,
      "description": "Maximum results (1-25)"
    },
    "query": {
      "type": "string",
      "maxLength": 100,
      "minLength": 2,
      "description": "Fund name, AMC or keywords, e.g. 'parag parikh flexi cap' or 'axis elss'"
    },
    "option": {
      "enum": [
        "growth",
        "idcw",
        "any"
      ],
      "type": "string",
      "default": "any",
      "description": "Only Growth or IDCW (dividend) options; default any"
    },
    "include_inactive": {
      "type": "boolean",
      "default": false,
      "description": "Include closed, matured or merged schemes"
    }
  }
}
    arguments 47 lines
  • get_fund_nav unknown never probed

    Get the latest official NAV and NAV date for one Indian mutual fund scheme by AMFI scheme code, with the previous NAV, 1M/3M/6M/1Y point-to-point returns, 3Y/5Y/10Y CAGR, CAGR since the NAV history starts, 52-week high and low, fund house, category, plan, option and history start date. Use when the user asks for a fund's NAV today or its returns. Returns are computed from NAVs only (before exit load and tax).

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "scheme_code"
  ],
  "properties": {
    "scheme_code": {
      "anyOf": [
        {
          "type": "integer",
          "maximum": 9007199254740991,
          "minimum": -9007199254740991
        },
        {
          "type": "string",
          "maxLength": 12,
          "minLength": 1
        }
      ],
      "description": "6-digit AMFI scheme code, e.g. 122639 (from search_mutual_funds)"
    }
  }
}
    arguments 24 lines
  • calculate_sip_returns unknown 58m ago

    Simulate a monthly SIP in one Indian mutual fund scheme using its actual historical NAVs: each instalment buys units at the NAV on its due date (or the next NAV date after a holiday). Returns the number of instalments, total invested, units, current value, absolute gain and XIRR, plus a year-by-year summary. Supports an optional annual step-up. Use for 'what would my SIP be worth' questions. Ignores stamp duty, exit load and tax; can't project future returns.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "scheme_code",
    "monthly_amount",
    "start_date"
  ],
  "properties": {
    "end_date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Valuation date (optional; defaults to the latest NAV date). No instalments after it in YYYY-MM-DD format"
    },
    "start_date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Date of the first instalment; later instalments fall on the same day each month in YYYY-MM-DD format"
    },
    "scheme_code": {
      "anyOf": [
        {
          "type": "integer",
          "maximum": 9007199254740991,
          "minimum": -9007199254740991
        },
        {
          "type": "string",
          "maxLength": 12,
          "minLength": 1
        }
      ],
      "description": "6-digit AMFI scheme code, e.g. 122639 (from search_mutual_funds)"
    },
    "monthly_amount": {
      "type": "number",
      "maximum": 10000000,
      "minimum": 100,
      "description": "Monthly SIP amount in rupees, e.g. 10000"
    },
    "annual_step_up_pct": {
      "type": "number",
      "default": 0,
      "maximum": 100,
      "minimum": 0,
      "description": "Optional yearly increase in the SIP amount, in percent (0 = flat SIP)"
    }
  }
}
    arguments 49 lines
  • compare_funds unknown 58m ago

    Compare 2 to 5 Indian mutual fund schemes side by side by AMFI scheme code: latest NAV, category, plan, option, 1M/3M/6M/1Y returns and 3Y/5Y/10Y CAGR, all measured to the same as-of date. Use when the user wants to compare funds' past performance. Flags mixed categories, Direct vs Regular, and IDCW options. It does not rank or recommend funds.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "scheme_codes"
  ],
  "properties": {
    "scheme_codes": {
      "type": "array",
      "items": {
        "anyOf": [
          {
            "type": "integer",
            "maximum": 9007199254740991,
            "minimum": -9007199254740991
          },
          {
            "type": "string",
            "maxLength": 12,
            "minLength": 1
          }
        ],
        "description": "6-digit AMFI scheme code, e.g. 122639 (from search_mutual_funds)"
      },
      "maxItems": 5,
      "minItems": 2,
      "description": "2 to 5 AMFI scheme codes"
    }
  }
}
    arguments 30 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.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id f919949aba122c7f.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/f919949aba122c7f/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/f919949aba122c7f/badge.svg)](https://brick.blue/agent/f919949aba122c7f?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

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.