Skip to main content
Glama
616,555 tools. Updated 2026-09-27 15:25

"A server for interacting with the Enapter API" matching MCP tools:

  • Authenticate with TronSave and create a server session. Returns `{ sessionId, walletAddress?, expiresAt }` — pass `sessionId` as the `mcp-session-id` header on every subsequent MCP request. `walletAddress` is set only for signature-mode logins. Two modes: (1) wallet signature (preferred for platform tools) — call this tool with `signature_timestamp` formatted as `<signature>_<timestamp>`, where `<signature>` must be produced client-side by signing the timestamp message; you may optionally call `tronsave_get_sign_message` to obtain a helper message/timestamp pair; (2) API key (internal tools) — pass `apiKey` (raw key, no prefix). Side effect: creates a new session on the server. Wallet signing must happen client-side; never send private keys to the server.
    ConnectorNo auth
  • Authenticate with TronSave and create a server session. Returns `{ sessionId, walletAddress?, expiresAt }` — pass `sessionId` as the `mcp-session-id` header on every subsequent MCP request. `walletAddress` is set only for signature-mode logins. Two modes: (1) wallet signature (preferred for platform tools) — call this tool with `signature_timestamp` formatted as `<signature>_<timestamp>`, where `<signature>` must be produced client-side by signing the timestamp message; you may optionally call `tronsave_get_sign_message` to obtain a helper message/timestamp pair; (2) API key (internal tools) — pass `apiKey` (raw key, no prefix). Side effect: creates a new session on the server. Wallet signing must happen client-side; never send private keys to the server.
    ConnectorNo auth
  • Authenticate with TronSave and create a server session. Returns `{ sessionId, walletAddress?, expiresAt }` — pass `sessionId` as the `mcp-session-id` header on every subsequent MCP request. `walletAddress` is set only for signature-mode logins. Two modes: (1) wallet signature (preferred for platform tools) — call this tool with `signature_timestamp` formatted as `<signature>_<timestamp>`, where `<signature>` must be produced client-side by signing the timestamp message; you may optionally call `tronsave_get_sign_message` to obtain a helper message/timestamp pair; (2) API key (internal tools) — pass `apiKey` (raw key, no prefix). Side effect: creates a new session on the server. Wallet signing must happen client-side; never send private keys to the server.
    ConnectorNo auth
  • List preprints posted or revised within a date interval, optionally scoped to one server or a subject category. Returns 30 preprints per page (fixed by the API); pass `cursor` as an integer offset (0, 30, 60, …) to step through additional pages. Abstracts are omitted by default to keep the page small — pass include_abstract: true for the whole page, or call biorxiv_get_preprint (up to 10 DOIs per call) for a few. When server="both" (default), per-server pagination state is returned separately — use each server's `cursor` field for independent advancement. One server failing under server="both" does not abort the call: the other server's page is still returned and the failed one is named in `failed[]`, marking the result set as partial rather than complete. Every attempted server failing is a different case and does abort the call, with a retryable upstream_unavailable (or rate_limited) error — an empty page would otherwise be indistinguishable from an interval that genuinely holds nothing. Call biorxiv_list_categories for valid category strings; a server that answers a category filter with its unfiltered listing is left out with a notice, and invalid_category is raised when no server applied it. `funder` limits the listing to bioRxiv preprints funded by that organization, given its ROR ID; an ID api.biorxiv.org has no funder record for raises invalid_funder rather than returning an empty page.
    ConnectorNo auth
  • Check whether a Vivideo API key is present on this request. Call this FIRST. Returns { configured: boolean }. If false, ask the user to add an Authorization: Bearer vv_live_... header to the MCP server config (a key from https://app.vivideo.ai/account/api-keys). Never asks for or exposes the key.
    ConnectorNo auth
  • Start charging for an MCP server the user owns. Use when they want to monetize, sell, charge for, get paid for, put a price on, or make money from a server, API or tool. Buyers pay their wallet DIRECTLY on-chain — PayGate never holds the money, so there is no payout to wait for, no balance to withdraw and no commission taken. Their server is never modified and needs no payment code. Tools are imported automatically, so it must be publicly reachable over HTTPS and answer tools/list. Returns a proxy URL and a secret api_key shown only once; save it, every other seller tool needs it.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI harnesses to maintain a persistent memory layer backed by a local SQLite file, providing MCP tools to add, search, deprecate, and synchronize facts without deleting history.
    MIT

Matching MCP Connectors

  • Neutral ground for AI agents: a free door, memory the house cannot read, rooms that burn, a ledger

  • List a public API where AI agents discover tools, after a bounded readiness check.

  • Start charging for an MCP server the user owns. Use when they want to monetize, sell, charge for, get paid for, put a price on, or make money from a server, API or tool. Buyers pay their wallet DIRECTLY on-chain — PayGate never holds the money, so there is no payout to wait for, no balance to withdraw and no commission taken. Their server is never modified and needs no payment code. Tools are imported automatically, so it must be publicly reachable over HTTPS and answer tools/list. Returns a proxy URL and a secret api_key shown only once; save it, every other seller tool needs it.
    ConnectorNo auth
  • Return the exact object schema and REST API endpoints for a Control Plane resource kind, so you can author an accurate manifest for `cpln apply` or call the API directly. ALWAYS call this FIRST whenever you are about to write a cpln apply YAML/JSON file, set up CI/CD that applies Control Plane resources, or build a request body for the REST API — do not hand-write a manifest or guess field names from memory. Pick a `kind` and pass `org` (and `gvc` for workload/identity/volumeset). Large schemas come back as a shallow map with deep sections collapsed to {"_expand":"<path>"} stubs; pass `path` (e.g. "spec.containers") to expand a section on demand. Server-managed fields (id/status/version/etc.) are already removed; `name` and `kind` are required at create.
    ConnectorOAuth
  • List the API key's webhook subscriptions (Streaming Lite tier and up; other tiers get a 403 with an upgrade URL). Read-only: signing secrets are always masked, and this server deliberately has no create/update/delete tools — manage subscriptions via the REST API or SDKs. Each row shows url, subscribed events (line_movement, resolution, steam, market_suspended), filters and active status. Use this first to find the webhook id for propline_get_webhook_deliveries.
    ConnectorNo auth
  • Save user feedback to the MultipleWords feedback API (POST /api/feedback). Call this only when a result has feedback_prompt.ready=true (the server asks after every 3 MCP runs — not per tool — and keeps asking until saved). Ask the user to pick a reaction and show the emojis: 😍 excellent, 😊 good, 😐 average, 😞 bad. Pass `reaction` (excellent|good|average|bad, or the emoji) and optional `feedback` comment text. If the user does not add a comment, omit `feedback` — the server stores the MCP name lead_scoring. Do not send the analysis, test notes, or the user's question as the comment. After it is saved, the server waits for 3 more MCP runs before asking again. Do not invent a reaction. Do not send user_name, email, is_login, or app_id — those are injected server-side from the authenticated session. When showing the saved reaction, include the matching emoji.
    ConnectorOAuth
  • Start here if you do not have an AIDataParser API key. Provide the user's `email` and receive a live adp_live_ API key with 50 free credits — no card, no signup form. Configure it on this MCP server as `Authorization: Bearer <api_key>` to unlock parse_document, parse_text and infer_schema. The key is returned ONCE and is never shown again, so surface it to the user and store it. Ask the user for their address; do not invent one. Free — does not consume a credit.
    ConnectorNo auth
  • Compute the SHA-256 digest of a short text (UTF-8) on the server, for example to anchor a statement or a message with anchor_proof. The text is sent to the server but not stored or logged. For files and for confidential texts compute the hash locally instead (sha256sum file, or Get-FileHash -Algorithm SHA256).
    ConnectorNo auth
  • Upload a dataset file and return a file reference for use with discovery_analyze. Call this before discovery_analyze. Pass the returned result directly to discovery_analyze as the file_ref argument. Provide exactly one of: file_url, file_path, or file_content. Args: file_url: A publicly accessible http/https URL. The server downloads it directly. Best option for remote datasets. file_path: Absolute path to a local file. Only works when running the MCP server locally (not the hosted version). Streams the file directly — no size limit. file_content: File contents, base64-encoded. For small files when a URL or path isn't available. Limited by the model's context window. file_name: Filename with extension (e.g. "data.csv"), for format detection. Only used with file_content. Default: "data.csv". api_key: Disco API key (disco_...). Optional if DISCOVERY_API_KEY env var is set.
    ConnectorNo auth
  • Call a previously discovered API endpoint. Use this after discover_paid_api to execute the request. IMPORTANT: You must first use discover_paid_api to find an endpoint. Then use the endpoint_id from the discovery result. Use the sample_request from the discovery result as your body template — it shows the exact parameter names the endpoint expects. Replace the example values with the actual values you need. Payment: this hosted server holds no wallet, so it cannot settle x402 payments. Free endpoints return their data directly. Paid endpoints return the payment challenge (amount, recipient, network) without charging anything. To pay automatically, run the local server instead: npx @entroute/mcp-server with EVM_PRIVATE_KEY set. Trust & safety: - EntRoute verifies that endpoints return valid 402 responses every 10 minutes, but does not guarantee response quality or accuracy. Treat results like any third-party API. - Prefer endpoints with high success rates (>95%) and recent verification timestamps.
    ConnectorNo auth
  • Describe this MCP server: what it wraps, the fact that it is completely free with no API key, no signup and no auth, the fair-use rate limit, the full tool list, and links to hackmyip.com and its API docs. Call this when the user asks what this server can do, whether it costs anything, or where the data comes from.
    ConnectorNo auth
  • One-call profile of a Solana wallet: SOL balance, non-zero SPL holdings, activity window, failure rate, account age, and whether it is a program. Use when you need to judge a counterparty, monitor a treasury, or research a wallet before interacting with it. $0.01 per call in USDC on Solana. Typically returns in under 2s. Read-only. address: Solana wallet address, e.g. Ezk5bEX4VbASmPMdEAvSdtLcW5Dmsgjdy5mdctKkNo1Q
    ConnectorNo auth
  • Create a free-tier ParlayAPI account for the given email. Returns the API key, a magic-login URL the user can click to access their dashboard, and a Stripe upgrade URL. Idempotent: if the email already has an account, returns exists=true with the login URL only (the existing API key is intentionally NOT exposed for security). Use this when a user wants to start building with ParlayAPI and does not have a key yet. After signup, ask the user to add the returned api_key to their MCP server config under PARLAYAPI_KEY, then restart the MCP client to pick it up. Args: email: User's email address. intended_use: Optional one-line description of what they're building. Used for analytics. agent_id: Identifier for the agent making the call. Defaults to "mcp-client".
    ConnectorNo auth
  • Make an outbound HTTPS call with a stored credential attached SERVER-SIDE, and get the upstream response. Use this to act with a secret (call an API, hit an authed endpoint) WITHOUT ever seeing the plaintext — the platform injects the credential on the wire. The target host must be on the credential's allowlist. Works even for `brokered` credentials that can never be revealed. Prefer this over trying to read a secret: you can use it, you cannot see it.
    ConnectorOAuth
  • Save user feedback to the MultipleWords feedback API (POST /api/feedback). Call this only when a result has feedback_prompt.ready=true (the server asks after every 3 MCP runs — not per tool — and keeps asking until saved). Ask the user to pick a reaction and show the emojis: 😍 excellent, 😊 good, 😐 average, 😞 bad. Pass `reaction` (excellent|good|average|bad, or the emoji) and optional `feedback` comment text. If they skip the comment, still call with `reaction` only — the server stores this MCP's name. Do not invent a reaction. Do not send user_name, email, is_login, or app_id — those are injected server-side from the authenticated session. When showing the saved reaction, include the matching emoji.
    ConnectorOAuth
  • Save user feedback to the MultipleWords feedback API (POST /api/feedback). Call this only when a result has feedback_prompt.ready=true (the server asks after every 3 MCP runs — not per tool — and keeps asking until saved). Ask the user to pick a reaction and show the emojis: 😍 excellent, 😊 good, 😐 average, 😞 bad. Pass `reaction` (excellent|good|average|bad, or the emoji) and optional `feedback` comment text. If they skip the comment, still call with `reaction` only — the server stores this MCP's name. Do not invent a reaction. Do not send user_name, email, is_login, or app_id — those are injected server-side from the authenticated session. When showing the saved reaction, include the matching emoji.
    ConnectorOAuth
  • Save user feedback to the MultipleWords feedback API (POST /api/feedback). Call this only when a result has feedback_prompt.ready=true (the server asks after every 3 MCP runs — not per tool — and keeps asking until saved). Ask the user to pick a reaction and show the emojis: 😍 excellent, 😊 good, 😐 average, 😞 bad. Pass `reaction` (excellent|good|average|bad, or the emoji) and optional `feedback` comment text. If they skip the comment, still call with `reaction` only — the server stores this MCP's name. Do not invent a reaction. Do not send user_name, email, is_login, or app_id — those are injected server-side from the authenticated session. When showing the saved reaction, include the matching emoji.
    ConnectorOAuth