_ registry / mcp streamable-http · checked 2h ago

instapi

https://instapi.co

Registry code: 191f5f80e38a178c

api record

Instagram data for agents. Call get_started first: it's free and shows your account status and how to get an API key.

endpoint
https://instapi.co/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 instapi live?
Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
Is instapi free to use?
Yes — the hub reached it with no key and no payment.
What tools does instapi have?
4 tools: instagram_user_posts, instagram_search, instagram_user_profile, get_started.
Is instapi 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
99.3%

90 days 99.5%· all time 99.5%

latency
279ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 378 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
used for
  • search instagram users and hashtags
  • get an instagram profile
  • fetch recent instagram posts
takes → gives
text → data
tools
4 reads
_ 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

_ what it can do 4 tools
1 open 3 never probed 1 of 4 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.

  • get_started reads open 24h ago

    Free, no auth. Service overview, pricing, current account status, and how to get an API key for the data tools.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • instagram_user_posts reads unknown never probed

    Fetch recent posts for an Instagram username, with images and videos AI-parsed into text descriptions. Costs 1 credit. Requires Authorization: Bearer sk_instapi_.... First fetch for a user can take up to ~60s while media is analyzed; cached users return fast.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "username"
      ],
      "properties": {
        "count": {
          "type": "integer",
          "default": 12,
          "maximum": 30,
          "description": "Number of most recent posts, newest first (default 12, max 30)",
          "exclusiveMinimum": 0
        },
        "username": {
          "type": "string",
          "minLength": 1,
          "description": "Instagram username, without @"
        }
      }
    }
    arguments 21 lines
  • instagram_search reads unknown 24h ago

    Search Instagram users, hashtags, and places by keyword. Costs 1 credit. Requires Authorization: Bearer sk_instapi_... on the MCP connection.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "minLength": 1,
          "description": "Search keyword, e.g. a name, brand, or topic"
        }
      }
    }
    arguments 14 lines
  • instagram_user_profile reads unknown never probed

    Public profile for an Instagram username: bio, links, follower/following/post counts, verified/private/business flags, category. Works for private accounts too. Costs 1 credit (refunded if the user doesn't exist). Requires Authorization: Bearer sk_instapi_....

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "username"
      ],
      "properties": {
        "username": {
          "type": "string",
          "minLength": 1,
          "description": "Instagram username (bare, @handle, or profile URL)"
        }
      }
    }
    arguments 14 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 191f5f80e38a178c.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/191f5f80e38a178c/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/191f5f80e38a178c/badge.svg)](https://brick.blue/agent/191f5f80e38a178c?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
80%

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.