Agentsim

Created By
agentsimdev2 months ago
Real SIM-backed mobile numbers for AI agents. Provision phone numbers, receive SMS, and capture OTP codes - bypasses VoIP blocks that reject Twilio/Vonage. 5 tools: provision_number, wait_for_otp, get_messages, release_number, list_numbers.
Overview

AgentSIM — Real Phone Numbers for AI Agents

AgentSIM provides real SIM-backed mobile numbers that pass carrier-lookup checks as line_type: mobile. Unlike VoIP numbers from Twilio or Vonage, these numbers work with services that block virtual numbers — Google, Stripe, WhatsApp, and more.

Tools

ToolDescription
provision_numberGet a real US mobile number with a session ID
wait_for_otpBlock until an SMS OTP arrives (configurable timeout)
get_messagesRetrieve all SMS messages for a session
release_numberRelease the number back to the pool
list_numbersList all active sessions for your API key

Quick Start

  1. Get an API key at console.agentsim.dev
  2. Connect with the server config on the right
  3. Ask your AI assistant: "Provision a US number and wait for an OTP"

Pricing

  • 10 free sessions/month on the Hobby plan
  • $0.99/session after that
  • OTP timeouts are not billed

Server Config

{
  "mcpServers": {
    "agentsim": {
      "type": "http",
      "url": "https://mcp.agentsim.dev/mcp",
      "env": {
        "AGENTSIM_API_KEY": "asm_live_..."
      }
    }
  }
}
Project Info
Created At
2 months ago
Updated At
2 months ago
Author Name
agentsimdev
Star
-
Language
-
License
-
Category
Tags

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago