"Creating a tool to replicate NowCerts API functionality" matching MCP tools:

• list_currenciesA

  PayramB

  Lists every blockchain currency PayRam supports on this node (chain code, network, currency code). Public endpoint — works with only PAYRAM_BASE_URL set, no API key or JWT required. Use this to discover valid blockchainCode/currencyCode values before creating payments or payouts.

  ConnectorNo auth

• create_productA

  KernelScanA

  Create a new product, run analysis, and return its initial stats. ``config_upload_id`` references a previously-staged .config that the caller POSTed to ``/api/configs/uploads`` over plain HTTP — the LLM does NOT emit the config text itself (a real kernel .config is ~100–200 KB and exceeds a single tool-call output budget). Workflow: 1. Caller / wrapper script: ``curl -H "Authorization: Bearer ks_live_..." \ -F "config_file=@.config" \ https://kernelscan.io/api/configs/uploads`` returns ``{config_upload_id, sha256, size_bytes, expires_at}``. 2. Pass that ``config_upload_id`` into this tool. Uploads are per-user, single-use, and expire 30 minutes after upload. Same gates as POST /api/products: free can't create products; paid plans are capped at their resolved product limit — read it (and any per-account override) from ``whoami.product_limit`` rather than assuming a fixed per-tier number. ``factor_ids`` are silently ignored unless the plan allows security factors (``whoami.can_use_factors``). Re-using a product name returns 409. Creating a product RUNS an analysis, so it spends one unit of the team's SHARED monthly analysis allowance (``whoami.monthly_analyses_used`` / ``monthly_analyses_limit``). When the allowance is exhausted the tool fails with "Monthly analysis limit reached (…/month) [429]". This is a durable monthly quota — NOT the transient per-call rate limit that also surfaces as 429: it will not clear until next month, so report it to the user instead of retrying. Check ``whoami`` before a batch of creates.

  ConnectorNo auth

• save_lead_messageA

  LinkedIn MCP Server (Salesbot)A

  Store a generated outreach message on a CRM lead so it becomes durable context — e.g. an email, an email follow-up, a LinkedIn message or LI follow-up. The CRM is a 'sponge': you save the copy here, then read it back later (get_lead_context / list_lead_messages) and push it to the right channel via that channel's own tool/MCP (e.g. Smartlead for email). Does NOT send anything. Pass message_id to update an existing draft instead of creating a new one.

  ConnectorNo auth

• dreamagent_list_global_integrationsA

  DreamAgent CloudA

  List the user's saved credentials (Global Integrations). ALWAYS call this before creating any bot project or asking the user for a token/API key. Saved credentials are referenced BY ID when creating projects: bot_token_integration_id for bot tokens, global_integration_ids for other keys. Secret values are never returned — only IDs and metadata (type, key name, verified, title). If nothing suitable is saved: direct the user to dreamagent.cloud → Settings → Global Integrations to add it (one-time, verified, reusable). Never ask the user to paste tokens in chat.

  ConnectorNo auth

• dreamagent_list_global_integrationsA

  DreamAgentA

  List the user's saved credentials (Global Integrations). ALWAYS call this before creating any bot project or asking the user for a token/API key. Saved credentials are referenced BY ID when creating projects: bot_token_integration_id for bot tokens, global_integration_ids for other keys. Secret values are never returned — only IDs and metadata (type, key name, verified, title). If nothing suitable is saved: direct the user to dreamagent.cloud → Settings → Global Integrations to add it (one-time, verified, reusable). Never ask the user to paste tokens in chat.

  ConnectorNo auth

• register_agentA

  LastPingA

  Requires an API key with the write scope or higher. Register a new autonomous agent in the project's agent registry, returning its id, slug and wire-up instructions in one call — so an agent can go from nothing to reporting in a single conversation. Call this ONCE per autonomous worker, not once per monitor. ATTACHMENT RULE: after registering, attach monitors to this agent by passing the returned agent_id (its id OR its slug) to create_monitor's agent_id parameter. Naming an agent that does not exist is an error (400 UNKNOWN_AGENT) — it is NEVER an implicit create, so re-running this tool with the same name is the only way to get a new agent_id to attach to. Re-registering with the same name is safe: the API derives a stable slug from name and rejects a duplicate slug rather than creating a second row.

  ConnectorNo auth

• get_photoA

  holiday-photo-plus-2A

  Display a holiday photo to the user by creating an HTML artifact that embeds the photo from its hosted URL. After calling this tool you MUST create an HTML artifact (type text/html) whose body is a single <img> tag pointing at the hosted URL returned in the result. Do not write a prose description, caption, or commentary — the user wants to view the photo, not read about it. Use list_photos first to discover valid IDs.

  ConnectorNo auth

• adsap_get_adA

  AdsapA

  Read ONE ad in full, live from Meta — its creative content (primary texts, headlines, descriptions, CTA, destination link, URL parameters, image hashes / video ids, Facebook Page and Instagram identity) plus status, timestamps, object_story_id / effective_object_story_id (the underlying post, which carries the ad's likes and comments) and the raw creative specs. Get the ad_id from adsap_list_ads or adsap_get_insights. Use it to inspect an ad's copy and media, to replicate an ad, or to answer 'what does this ad say / link to?'. Read-only — to CHANGE a live ad's creative use adsap_replace_ad_creative.

  ConnectorAPI key

• budget_getA

  CorroborateMeA

  Read remaining quotas and plan entitlement for the authenticated company. Call this when you need to know whether an active plan is in effect before registering OIDC clients or creating login links. Minting an API key does not require an active plan. Requires a company API key (aa_...) or an MCP OAuth access token. Returns planId, planStatus, periodYm, included, used, remaining, and hardCap. It does not change billing or charge a card. To start a human Pro checkout, use billing_checkout. billing_machine_pay only returns prepaid REST instructions. To manage an existing Stripe subscription, use billing_portal.

  ConnectorAPI key

• get_planA

  Sweeppea MCPA

  Get the current account's plan and usage telemetry. Returns the AUTHORITATIVE plan limits AND real-time usage so you can warn the user when they are approaching a cap. Key fields: `plan.Name` (plan name to mention to the user), `plan.Settings.MaxSweepstakesAllowed` (single cap on TOTAL sweepstakes — there is NO separate active vs total limit, the API treats them as one count), `plan.Settings.MaxParticipantsAllowed`, `plan.Settings.MaxStorageSize` (GB), `plan.Settings.MaxApiCallsAllowed`, `plan.Settings.SubscriptionPrice`; `telemetry.DataConsumed` (GB used now), `telemetry.APICalls` (calls used this period). Each account can have a custom plan — these values OVERRIDE any default numbers mentioned in other tool descriptions or instructions. Call this once per session before creating/cloning sweepstakes, before quoting limits or usage to the user, or when the user asks about pricing, billing, or feature availability. # get_plan ## When to call BEFORE: creating/cloning a sweepstakes, quoting limits or usage to the user, suggesting an upgrade, or answering questions about pricing, billing, or which features are enabled. ONCE per session — cache the result mentally; the response rarely changes mid-session. ## Why authoritative `plan.Settings.MaxSweepstakesAllowed` is a SINGLE per-account cap. The API does NOT distinguish "active" from "total" — there is only one count. Different accounts can have very different plans (admin, enterprise, default). Always trust the values returned by this tool over any number mentioned elsewhere in tool descriptions or instructions. ## Reading the response - `plan.Name` — say this name to the user when discussing limits (e.g. "your plan 'X' allows...") - `plan.Settings.MaxSweepstakesAllowed` — total sweepstakes cap - `plan.Settings.MaxParticipantsAllowed` — total participants in the account - `plan.Settings.MaxStorageSize` — GB - `plan.Settings.MaxApiCallsAllowed` — API call quota - `plan.Settings.PaidModule*` (15 booleans) — which features are enabled vs gated - `telemetry.DataConsumed` — GB used now (compare against MaxStorageSize) - `telemetry.APICalls` — calls used this period (compare against MaxApiCallsAllowed) If usage is >= 80% of any cap, warn the user proactively.

  ConnectorNo auth

• create_snapshotA

  BorealHostB

  Create a local container snapshot (async). Runs in background — returns immediately with status "creating". Poll list_snapshots() to check when status becomes "completed" or "failed". Available for VPS, dedicated, and cloud plans (any plan with max_snapshots > 0). Local snapshots are stored on the host disk and count against disk quota. Requires: API key with write scope. Args: slug: Site identifier description: Optional description (max 200 chars) Returns: {"id": "uuid", "name": "snap-...", "status": "creating", "storage_type": "local", "message": "Snapshot started. Poll list_snapshots() to check status."} Errors: VALIDATION_ERROR: Max snapshots reached or insufficient disk quota

  ConnectorNo auth

• video_to_audioA

  Media Generator — Images, Videos & AudiosA

  Input: A muted video URL along with a textual prompt describing the desired audio. Output: We will return the video URL with the applied audio. Functionality: This tool now takes a muted video and a text prompt as input. It generates an audio track based on the provided prompt and applies this audio to the video, resulting in a video with integrated sound. Steps: 1. We will get the user_id from the request context. 2. We will validate the user's generation tokens. 3. We will call the Audio Application API with the muted video URL and the provided prompt. 4. The API will generate the audio from the prompt and merge it with the muted video, returning a JSON response with the updated video URL. 5. We will return the updated video URL to the user. INSTRUCTION FOR CLIENT MODEL: - Extract the required input parameters 'video_url' (type: string, URL) and 'prompt' (type: string, describing the desired audio) from the user's prompt. - Ignore any extraneous information in the user's input. - Pass the extracted values to this tool as 'video_url' and 'prompt'. - Example: For user input "Add dramatic orchestral music to this video https://example.com/video.mp4", extract 'video_url' as 'https://example.com/video.mp4' and 'prompt' as 'dramatic orchestral music'.

  ConnectorOAuth

• create-share-linkA

  Music StudioA

  Create a hosted music share link only when the user asks to share or store a piece online. Uploads the supplied score or pattern to MCP Music Studio for 30 days; anyone with the link can view and play it without signing in. Creating the same share again refreshes its expiry. Playback does not require this tool. Provide kind 'score' with score, or kind 'play' with pattern. Never include private information or secrets.

  ConnectorNo auth

• string_helpA

  STRING Database MCP ServerA

  Provides explanatory text for STRING features and limitations. Use this tool when the user question involves: - What is STRING is or how to use the tool (how_to_use_string, cytoscape) - functionality not available via MCP tools (e.g. GSEA, regulatory networks, large datasets). - meaning of the lines in the network (line_colors)

  ConnectorNo auth

• scan_for_secretsA

  secret-scannerA

  Scan a pasted config, file, code snippet, or blob for exposed credentials and obvious security misconfigurations. Use whenever a user shares a .env, docker-compose.yml, nginx.conf, JSON/YAML config, or any text and asks "is this safe to share/commit?", "any leaked API keys/secrets?", or "what's misconfigured?". Detects cloud credentials, Stripe/GitHub/GitLab tokens, OpenAI/Anthropic/Gemini/Hugging Face/Groq/Replicate keys, private-key blocks, JWTs, DB connection strings, plus misconfigs like debug-on, 0.0.0.0 binds, disabled TLS verification, privileged containers, and weak passwords. Deterministic. It analyzes the provided text and returns findings only — it never stores, transmits, or requires any live credential.

  ConnectorNo auth

• view-hmr-unit-testsA

  hmrA

  The unit tests (code examples) for HMR. Always call `learn-hmr-basics` and `view-hmr-core-sources` to learn the core functionality before calling this tool. These files are the unit tests for the HMR library, which demonstrate the best practices and common coding patterns of using the library. You should use this tool when you need to write some code using the HMR library (maybe for reactive programming or implementing some integration). The response is identical to the MCP resource with the same name. Only use it once and prefer this tool to that resource if you can choose.

  ConnectorNo auth

• signupA

  UnphurlA

  Create a new Unphurl account. Returns an API key (shown once, store it securely). After signup, the user must check their email and click the verification link. The API key won't work for URL checks until the email is verified. Verification link expires after 24 hours. If the link expires, use the "resend_verification" tool to request a new one. The account starts with 20 free pipeline check credits so the user can test with real URLs. Known domain lookups (google.com, github.com, etc.) and cached domain lookups are always free. To check more unknown domains through the full analysis pipeline, the user can purchase credits via the "purchase" tool. Once the user has their API key, they need to add it to their MCP server configuration as UNPHURL_API_KEY. This tool does not require an API key.

  ConnectorNo auth

• show_defaultsA

  UnphurlA

  Show all 25 scoring signals with their default weights and descriptions. This is the baseline scoring that applies when no custom profile is specified. Use this to understand what each signal means and how much it contributes to the score before creating custom profiles. Profiles are sparse overrides on top of these defaults. This tool does not require an API key. The defaults are hardcoded and always available.

  ConnectorNo auth

• create_b2_snapshotA

  BorealHostB

  Create a B2 cloud-backed snapshot (zero local disk, async). Streams container data directly to Backblaze B2 via restic. No local disk impact — billed separately at cost+5%. Runs in background — returns immediately with status "creating". Poll list_snapshots() to check when status becomes "completed". Only available for VPS plans. Requires: API key with write scope. Args: slug: Site identifier description: Optional description (max 200 chars) Returns: {"id": "uuid", "name": "...", "status": "creating", "storage_type": "b2", "message": "B2 cloud snapshot started. Poll list_snapshots()..."} Errors: VALIDATION_ERROR: Not a VPS plan or max snapshots reached

  ConnectorNo auth

• api_statusA

  Cannon StudioA

  Check authenticated Cannon Studio account/API connectivity before estimating or creating requests. Requires OAuth or a developer API key; may update key/token usage metadata, but does not spend credits, enqueue jobs, change assets, or expose secrets.

  ConnectorNo auth

• estimate_generation_costA

  Cannon StudioA

  Estimate credits for a Cannon Studio generation request before creating billable work. Requires OAuth or a developer API key; it may update key/token usage metadata but does not spend credits, enqueue jobs, or change assets. Use get_api_operation first if operation or input fields are unclear, then pass the same operation/input pair to create_generation_request after user approval.

  ConnectorNo auth