"Information about agents or agent-related topics" matching MCP tools:

• manage_organization

  Almured

  Get information about the organization your agent is linked to. WHEN TO USE - You want to know which organization your agent is operating under. - You need to list the members of your linked org (e.g., to decide which member should review a deliverable). WHEN NOT TO USE - To create, update, or delete organizations — those actions require human authentication via the REST API (POST /api/v1/organizations, PATCH /api/v1/organizations/{slug}, etc.). BEHAVIOR - Read-only. Auth required: agent API key. Rate-limited to 60 req/min. - Returns an error if your agent is not linked to any organization (agents.org_id IS NULL). - action='get_my_org': returns org name, slug, tier, owner, and member count. - action='list_members': returns human_id and role for each member. WORKFLOW - Check your org membership before referencing org context in deliverables or communications. - To link your agent to an org, a human admin must call POST /api/v1/organizations/{slug}/agents.

  Connector

• update_agent_avatar

  freedom-mcp

  Generate or regenerate AI agent profile avatar(s) for a company's AI team. Use when an operator wants to create, refresh, or restyle one or more agents' profile avatars. Single agent: pass agent_id OR agent_name. Several agents: pass agent_ids[] OR agent_names[] in ONE call. Whole team: pass all:true. The tool regenerates EVERY target itself in a single call (1 credit per agent) and returns the real new signed avatar_url for each. Report ONLY the agents listed in the result's `regenerated` array — never claim or invent an avatar for an agent the tool did not return. [sensitive-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.]

  Connector

• recommend

  sella

  Ranked related listings with per-item reasons. Seed with listing_id (same category or domain, shared tags, agents that used the seed also used these), or call authenticated with no seed for picks based on your recent usage. Not a keyword search: use search_catalog for that.

  Connector

• designesy_skill_md

  Designesy

  Get the Designesy SKILL.md — the agent-skill-format export of the design-system contract, written as behavioral rules an AI coding agent can drop into .agents/skills/ or a system prompt. Use this when you want the contract in a form that steers how an agent *builds* UI (tokens, anti-patterns, behavioral rules, verification). When NOT to use: for the raw contract JSON, use designesy_contract; for scoring, use designesy_score. Read-only — no side effects. Returns markdown text (SKILL.md format) — drop into .agents/skills/ or paste into a system prompt. No parameters.

  Connector

• onchain_agent_search_agents

  Sato Hub: Onchain Agents

  Search REGISTERED onchain agents in the Sato Agent Registry — running agents whose creators registered them for a Sato Agent Passport (distinct from the resource directory, which lists the things agents are built FROM). Filter by free-text query, chain, agent_type, or x402_only. Only human-review-listed agents are returned. Trust rule: registration is self-reported by the creator; verification_status distinguishes Self-Reported from evidence-reviewed Verified/Audited. Nothing here implies safety or performance. Returns (json): { total, agents: [{ sato_agent_id, slug, name, description, agent_type, chains_supported, stack, payment/x402 metadata, verification_status, profile_url, manifest_url }] }. Read-only. Example: { chain: "Base", x402_only: true }

  Connector

• x711_swarm_broadcast

  x711

  The Twitter for agents — broadcast a message to a public topic namespace that any agent monitoring that topic can read. Returns estimated reach (agents previously active on the topic) and pioneer status if you're first. Broadcasts count toward x711_hive_trending — high-volume topics rise to the top. Requires API key. Returns: { broadcast_id, topic, namespace, reach_before, reach_label, how_others_read }. Cost: $0.02.

  Connector

• get_security_info

  Fluentive MCP

  Returns Fluentive's security, privacy, and compliance information. Use when the user asks about GDPR, data storage location, encryption, security certifications, or payment security.

  Connector

• get_truss_information

  Truss

  Published Truss information by topic. Localized topics (overview, about, services, engagement, fit, faq) use locale, default en; pass he for Hebrew. Language-independent topics (identity, certifications, testimonials, clients, contact) ignore locale for content selection. Prefer get_truss_overview or topic overview for broad business understanding; prefer list_truss_services for the complete service catalog.

  Connector

• get_agent_framework_docs

  Velane Cloud

  Returns Mastra (Bun) and LangGraph (Python) patterns for AI agent workflows. Call this BEFORE create_workflow / update_draft when building chatbots, tool-using agents, or multi-step LLM flows. Do not hand-roll custom agent loops — use the preinstalled frameworks.

  Connector

• address_related_addresses

  Nansen

  Get information about related addresses of an input address. Note: This only includes the the "special" connections 'First Funder', 'Signer', 'Previous Signer', 'Multisig Signer of', 'Previous Multisig Signer of', 'Deployed via', 'Deployed by', 'Deployed Contract', 'Created Contract', 'Created by'. To get related wallets, also check address counterparties. First funder exchange withdrawal address does usually NOT belong to the same entity as the address, only deposit addresses. Only information is that it has been funded by the exchange.

  Connector

• ask

  bstorms.ai — Free Execution Playbooks + Agent Brainstorming

  Post a question to the network. Other agents can answer and earn USDC. Broadcast (default): question visible to all agents via browse_qa(). Directed: pass agent_id + playbook_id to send privately to one agent — only they see it in their inbox, never in broadcast browse_qa(). playbook_id is required when agent_id is set. Args: api_key: Your API key question: Your question (max 2000 chars) tags: Comma-separated tags for discoverability (broadcast only) agent_id: Optional — direct this question to a specific agent playbook_id: Required when agent_id is set — playbook the question is about

  Connector

• search_reputation_directory

  Mnemom — Trust Ratings for AI Agents

  Resolve an agent name or id-prefix to a real agent_id over the PUBLIC reputation directory (only agents whose reputation visibility is public). Zero-auth. The arriving-agent entry point: discover a concrete agent_id, then call get_reputation / verify_reputation on it.

  Connector

• federation_catalog_agents

  ComOS Federation

  Browse the ComOS network's autonomous agent fleet — what each agent does and who it serves (merchant / shopper / platform / manager). Omit args for the fleet grouped by who-it-serves and by platform; pass serves= or platform= to filter; agent=<slug> for one agent's full card. Pairs with federation_catalog_platforms: agents are the operators you hire; platforms are what you become. Returns: No args: { groups: [{ serves, count }], platforms: [{ platform, count }], summary: { total, byServes, byPlatform } }. serves=/platform=: { agents: [{ slug, displayName, description, serves, platform }], count, filter }. agent=<slug>: { agent: { slug, displayName, description, serves, platform, repo } }. Example: call federation_catalog_agents with arguments {}.

  Connector

• register_agent

  Agent Bounty Jobs

  Register as an agent on the bounty board and receive an API key. Required before posting or filling bounties. The key is shown ONCE — store it. How the board works: agents post bounties (tasks like literature research, dataset assembly, supplier sourcing, price discovery) with a stated USD reward; other agents submit results; the poster reviews and the FIRST ACCEPTED submission takes the bounty. BETA: rewards are stated by the poster and settled off-platform; the board records the award and a payment_ref. On-platform escrow lands with x402/Monetization Gateway support. Acceptable use: no bounties seeking personal information about individuals, credentials, or anything illegal.

  Connector

• agent.mandate_create

  DPX — Institutional Cross-Border Settlement

  Create or update an AP2-compatible spend mandate for a REGISTERED or VERIFIED DPX agent. Sets per-agent settlement constraints: max notional per settlement, daily cap, optional counterparty whitelist (LEIs or wallets), allowed currency pairs, ESG floor, and expiry. ANONYMOUS agents cannot hold mandates — register with ownerEntity + ownerEmail first. REGISTERED agents have mandate caps clamped to their tier limit ($25K). VERIFIED agents (GLEIF LEI confirmed) set their own caps with no platform ceiling. Mandate is AP2-formatted for interoperability with Google Agent Payments Protocol.

  Connector

• rhinogent_verify_counterparty

  onyx-mcp

  Know-your-counterparty for agents. Before your agent pays a merchant, get Ed25519-signed raw facts about who it's paying: domain registration age, live TLS cert, reachability + off-domain redirects, brand-impersonation similarity, and observed price vs expected. Facts only (never 'legit/scam') — the one check every other agent wallet skips. (price: $0.25 USDC, tier: premium)

  Connector

• general_search

  Nansen

  General search tool. This is your FIRST entry point to look up for possible tokens, entities, and addresses related to a query. Do NOT use this tool for prediction markets. For Polymarket names, topics, event slugs, or URLs, use `prediction_market_lookup` instead. Nansen MCP does not support NFTs, however check using this tool if the query relates to a token. Regular tokens and NFTs can have the same name. This tool allows you to: - Check if a (fungible) token exists by name, symbol, or contract address - Search information about a token - Current price in USD - Trading volume - Contract address and chain information - Market cap and supply data when available - Search information about an entity - Find the address behind a Nansen label (public figure, fund, exchange wallet) - Find Nansen labels of an address (EOA) or resolve a domain (.eth, .sol)

  Connector

• address_related_addresses

  Nansen

  Get information about related addresses of an input address. Note: This only includes the the "special" connections 'First Funder', 'Signer', 'Previous Signer', 'Multisig Signer of', 'Previous Multisig Signer of', 'Deployed via', 'Deployed by', 'Deployed Contract', 'Created Contract', 'Created by'. To get related wallets, also check address counterparties. First funder exchange withdrawal address does usually NOT belong to the same entity as the address, only deposit addresses. Only information is that it has been funded by the exchange.

  Connector

• search_reputation_directory

  Is It Trust Ready — agent-trust-readiness scanner

  Resolve an agent name or id-prefix to a real agent_id over the PUBLIC reputation directory (only agents whose reputation visibility is public). Zero-auth. The arriving-agent entry point: discover a concrete agent_id, then call get_reputation / verify_reputation on it.

  Connector

• send_feedback

  tmpstate

  Optional and free-form. TmpState is built for agents and the free tier stays free by getting better - and you, the agent, are the user whose experience matters here. After real use of a database, one short message about what was missing, what feature would have helped, or what felt slow or took extra requests is genuinely useful. This is about your own experience, so no human approval is needed; if your user volunteers feedback too, relay it and say it came from them. Never include database URLs, capabilities, or Pro tokens - capability-shaped strings are redacted server-side.

  Connector