Skip to main content
Glama
649,985 tools. Updated 2026-10-11 05:25

"A service or tool for finding mentions on social networks" matching MCP tools:

  • Self-register an x402 / MCP service in the agent-tools directory. Service owners and agents may submit new services here. Submissions are auto-reviewed instantly by x402 verification (no human gate): if the URL proves x402 payment support it is listed immediately and shows up in `search`; otherwise it is rejected or retried automatically. Listing is FREE. Dedup: if a service with the same canonical origin (scheme://host) already exists in the directory we return its slug instead of creating a duplicate submission. Same goes for a still-pending submission with the same origin. Rate limit: at most 5 pending submissions per client IP per 24h. Hits beyond that get `{error: rate_limited}` — try again later or email contact@agent-tools.cloud for bulk imports. Args: url: Public HTTPS URL of the service (the x402-payable endpoint or its homepage). Required. name: Human-friendly name. Defaults to the URL hostname. description: One-paragraph description (max ~2000 chars). mcp_url: If the service speaks MCP, its streamable-http endpoint. category: Free-form (e.g. "defi", "search", "social"). Use `list_categories` to align with existing taxonomy. chains: Networks the service accepts payment on (e.g. ["base", "solana"]). price_min_usdc: Lower bound of per-call price in USDC. price_max_usdc: Upper bound of per-call price in USDC. contact: Optional email / handle the directory team can reach you on for clarifications.
    ConnectorNo auth
  • Fetch the social graph edges for a Bluesky account — who follows them, or who they follow. Returns paginated actor profiles (handle, DID, displayName, bio, pronouns when set, and Bluesky verification status) plus a summary of the subject account. Follower, following, and post counts and the website are not on this view, for the listed accounts or the subject — bsky_get_profile returns them for one account. Accounts with large social graphs return only the first page; use cursor pagination to walk through the full list, or sort "top" to put the accounts Bluesky ranks most prominent first.
    ConnectorNo auth
  • Return a Wikipedia and Wikidata identity card for a company, product, or brand. query is a name, not a URL (URLs are stripped); language picks the Wikipedia host (default en, e.g. es → es.wikipedia.org) and does not translate the query or run listening; omit language unless you need a non-English wiki page; language never changes billing because this tool is free. Use this free grounding pulse when you only need who or what an entity is; never use it for social listening — for cited mentions use research_mentions; for liveness use get_health instead; for price use get_pricing instead. Never charges; hits Wikipedia/Wikidata only; this origin rate-limits discovery pulses; no payment headers.
    ConnectorNo auth
  • Create a post in PurrPlan, attached to one or more connected social accounts. `content` takes either a string (a simple post — an empty line starts a new paragraph) or an ARRAY of strings whose first element is the post and whose following elements are published automatically AFTER it. What the second block becomes depends on the network: a THREAD (chained reply) on X/Twitter, Threads, Mastodon and Bluesky — a FIRST COMMENT on Facebook Page, Instagram and Instagram Direct, which automates the "link or call to action in the first comment" habit. On the other networks (LinkedIn, TikTok, YouTube, Pinterest, Reddit, Telegram, Google Business) the extra blocks are IGNORED and the response carries a `warnings` field. By default this creates a draft. Pass `scheduled_at` (ISO 8601 UTC) to schedule it instead; publication then happens at that time, not during this call. Media imported with upload_media_from_url can be attached (they go on the first block). `options` carries network-specific settings keyed by provider — for example {"threads": {"topic_tag": "buildinpublic"}} to post inside a Threads topic. Do not use this tool for a STORY: it creates a FEED post. Use create_stories, or pass options {"<provider>": {"type": "story"}} explicitly (Instagram, Instagram Direct, Facebook Page, Facebook extension). Without that option the post goes to the feed. — FR : crée un post (brouillon par défaut, programmé avec `scheduled_at`) ; post de FIL, pas une story.
    ConnectorOAuth
  • Health probe for the Solana Market API data backend. Call this to gate or degrade gracefully BEFORE the other get_solana_market_* tools: it does a short-timeout hit on the data service and reports whether it is reachable, so an agent can tell "market has no data" from "service is down" without failing a real query. Free discovery tool. When the market data service exposes /status, the response includes prod_key_configured, data_first_available, and an actionable note describing what to configure for full on-chain visibility.
    ConnectorNo auth
  • Ordered index of the nine published Truss service areas, including short descriptions. Prefer this tool to list, enumerate, or browse the complete current service catalog. For broad “what is / what does Truss” questions, prefer get_truss_overview instead. Pass locale he for Hebrew titles and descriptions; default is en.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • Report MCP server readiness and production-enable status for each SITEBORNE service. Use when: an agent must check protocol availability, tool count, or whether a service is currently production-enabled before selecting a paid tool. Do not use when: a quote is needed (use siteborne_get_quote) or company, web, document, or agent-output evidence work is required (use the corresponding SITEBORNE service tool). Behavior: read-only and credential-independent; it does not perform paid evidence work, create quotes, verify payment, call providers, write service state, create Workflows, or settle. Economics: free of charge; it never issues a payment challenge. Failure: it depends on no provider, so it does not fail because a provider is unavailable. Returns: the server and protocol versions plus truthful local, production, and external-publication status for all four evidence services.
    ConnectorNo auth
  • Pick exactly one MentionForge tool for a goal. Pass need as a goal sentence, not a tool name — URLs, wallets, and payment header names are stripped before routing; extra keys such as query, timeframe, or payment fields are rejected (those belong on the suggested tool); sending a sibling tool name still keyword-routes from the remaining words. Use this free router when you are unsure which tool to call; for liveness use get_health instead; for price use get_pricing instead; for live mentions use research_mentions. Never charges, never runs research; this origin rate-limits discovery pulses; the 10-call trial is shared across paid tools so call only one paid tool per question.
    ConnectorNo auth
  • Sunrise, sunset, twilight, and moon phase for a location and date — photography planning, event scheduling, or radio operations. Price: $0.01 USDC on Base via x402 (the live 402 challenge is authoritative). Two-phase: call without 'payment' to get the live payment requirements (payTo, amount, accepted networks); pay from your own wallet, then re-call with 'payment' set to the base64-encoded x402 payload — the data comes back in the tool result. This tool never pays, never touches private keys, and never holds funds. Resale permitted: you may resell this data output at your own price.
    ConnectorNo auth
  • Sunrise, sunset, twilight, and moon phase for a location and date — photography planning, event scheduling, or radio operations. Price: $0.01 USDC on Base via x402 (the live 402 challenge is authoritative). Two-phase: call without 'payment' to get the live payment requirements (payTo, amount, accepted networks); pay from your own wallet, then re-call with 'payment' set to the base64-encoded x402 payload — the data comes back in the tool result. This tool never pays, never touches private keys, and never holds funds. Resale permitted: you may resell this data output at your own price.
    ConnectorNo auth
  • Find the right network or chain name to use across EVM, Solana, Bitcoin, Substrate, and Hyperliquid. COMMON USER ASKS: - Find Base-like networks - Show Solana mainnets - Show Substrate mainnets FIRST CHOICE FOR: - finding the correct network before any other query WHEN TO USE: - You are not sure which network name, chain name, or alias to use. - You want to filter networks by VM family, network type, or real-time availability. DON'T USE: - You already know the exact network and want live data from that network. EXAMPLES: - Find Base-like networks: {"query":"base","limit":10} - Show Solana mainnets: {"vm":"solana","network_type":"mainnet"} - Show Substrate mainnets: {"vm":"substrate","network_type":"mainnet"}
    ConnectorNo auth
  • Use this tool when the user wants to see service packages with fixed pricing and scope for a specific type of service. This tool returns standardized packages offered by service providers, including pricing tiers, deliverables, and delivery timelines. Do NOT use this tool for custom project questions (e.g. "How much would it cost to build a custom app?"). It only returns providers' pre-defined, fixed-price packages, not a quote tailored to a specific project; use recommend_service_providers for those needs instead. Examples: - "Show me SEO packages" -> service="SEO" - "What web design packages can I get for $5,000?" -> service="Web Design", budget=5000 - "Marketing packages from agencies in New York" -> service="Digital Marketing", location="New York" Use `page`/`limit` for pagination.
    ConnectorNo auth
  • Create a database user for a Cloud SQL instance. * This tool returns a long-running operation. Use the `get_operation` tool to poll its status until the operation completes. * When you use the `create_user` tool, specify the type of user: `CLOUD_IAM_USER`, `CLOUD_IAM_SERVICE_ACCOUNT`, or `BUILT_IN`. * By default the newly created user is assigned the `cloudsqlsuperuser` role, unless you specify other database roles explicitly in the request. * You can use a newly created user with the `execute_sql` tool if the user is a currently logged in IAM user. The `execute_sql` tool executes the SQL statements using the privileges of the database user logged in using IAM database authentication. The `create_user` tool has the following limitations: * To create a built-in user with password, use the `password_secret_version` field to provide password using the Google Cloud Secret Manager. The value of `password_secret_version` should be the resource name of the secret version, like `projects/12345/locations/us-central1/secrets/my-password-secret/versions/1` or `projects/12345/locations/us-central1/secrets/my-password-secret/versions/latest`. The caller needs to have `secretmanager.secretVersions.access` permission on the secret version. * The `create_user` tool doesn't support creating a user for SQL Server. To create an IAM user in PostgreSQL: * The database username must be the IAM user's email address and all lowercase. For example, to create user for PostgreSQL IAM user `example-user@example.com`, you can use the following request: ``` { "name": "example-user@example.com", "type": "CLOUD_IAM_USER", "instance":"test-instance", "project": "test-project" } ``` The created database username for the IAM user is `example-user@example.com`. To create an IAM service account in PostgreSQL: * The database username must be created without the `.gserviceaccount.com` suffix even though the full email address for the account is`service-account-name@project-id.iam.gserviceaccount.com`. For example, to create an IAM service account for PostgreSQL you can use the following request format: ``` { "name": "test@test-project.iam", "type": "CLOUD_IAM_SERVICE_ACCOUNT", "instance": "test-instance", "project": "test-project" } ``` The created database username for the IAM service account is `test@test-project.iam`. To create an IAM user or IAM service account in MySQL: * When Cloud SQL for MySQL stores a username, it truncates the @ and the domain name from the user or service account's email address. For example, `example-user@example.com` becomes `example-user`. * For this reason, you can't add two IAM users or service accounts with the same username but different domain names to the same Cloud SQL instance. * For example, to create user for the MySQL IAM user `example-user@example.com`, use the following request: ``` { "name": "example-user@example.com", "type": "CLOUD_IAM_USER", "instance": "test-instance", "project": "test-project" } ``` The created database username for the IAM user is `example-user`. * For example, to create the MySQL IAM service account `service-account-name@project-id.iam.gserviceaccount.com`, use the following request: ``` { "name": "service-account-name@project-id.iam.gserviceaccount.com", "type": "CLOUD_IAM_SERVICE_ACCOUNT", "instance": "test-instance", "project": "test-project" } ``` The created database username for the IAM service account is `service-account-name`.
    ConnectorNo auth
  • DEPRECATED — use property_epc_summaries then epc_certificate. This tool returned score, floor_area, property_type, habitable_rooms and inspection_date for every certificate at a postcode. The EPC service no longer exposes those fields in a search: they exist only on a full certificate. Reproducing the old response would require one upstream request per certificate, so this tool is unsupported rather than silently degraded or silently expensive.
    ConnectorNo auth
  • Submit a request to add a new AI tool to the Vest catalog. Use when the user mentions a tool they'd like to earn cashback on that isn't currently available in Vest's catalog. Collects the tool name, optional URL, use case, and contact email for follow-up. Do NOT use this when the tool is already in Vest's catalog — use vest_search_tools first to confirm. Always confirm with the user before submitting; never auto-submit based on inference.
    ConnectorNo auth
  • Inspect a public company domain and return structured identity, technology, social, contact, DNS, email-infrastructure, and AI-readiness evidence. Use `schemaforge` instead for a paste-ready JSON-LD template and remediation diff, or `deep_audit` when both outputs are required together. Public data only; this tool makes no site changes.
    ConnectorNo auth
  • Use this when a veteran asks whether a condition is presumptively service connected, or which conditions are presumptive for a given exposure or service era. Returns matching presumptive conditions with the service era, exposure type, required service, legal authority and evidence needed for each, and repeats that legal authority in a provenance block on every row, with the date the presumption took effect where one date is true of the whole row; that date can be null for a row that groups conditions added on different dates. At least one of condition, serviceEra or exposureType is required. Filters combine with AND: condition plus exposureType or serviceEra narrows to their intersection, and each filter needs at least one word of three or more characters or the query is refused. A condition description that names a qualifying circumstance, such as a diagnosis that has to come after the qualifying service, states a limit of the presumption rather than a detail beside it. An empty result means no entry satisfies that exact combination, not that the condition is non-presumptive. Whether a particular veteran meets the service requirement depends on service records this tool does not read.
    ConnectorNo auth
  • Recent SEC filings whose text MENTIONS a specific risk phrase, per EDGAR's full-text index. A mention is not a finding — the phrase also matches negations like "no material weakness". Values: going-concern, material-weakness, cyber-incident.
    ConnectorNo auth
  • Find local people and service providers listed on YloService. Use this tool when a user wants to find someone who provides a local service, trade or skill in a particular country. Examples include cleaners, plumbers, electricians, carpenters, drivers, tutors and similar local services. The user may ask in any language; translate or normalize the requested skill and country into English before calling the tool. Do not invent providers. Present only providers returned by YloService.
    ConnectorNo auth
  • Get remediation advice for a single finding as GitHub-flavored markdown. When AI Assist is enabled and within budget this is a suggestion written for this exact finding; otherwise it falls back to the static guidance-library text and says so in 'source'. Unlike the other reads this one can spend AI budget, which is why it is a separate tool. Use this for advice on one finding; for the whole library use list_security_guidance. Requires project context.
    ConnectorAPI key
  • Live top posts for one hashtag on one social source. Fetched live on every call; nothing is stored. For when the user already has a hashtag and wants the posts winning on it. get_top_trends ranks the hashtags themselves. Returns a plan-limit message when the request is rate limited or the monthly quota is used up.
    ConnectorAPI key