"A resource for finding logos of all companies" matching MCP tools:

• well_add_contact_channel

  Well

  Add a contact channel to a company or person. Wraps the resource-scoped REST endpoints (POST /v1/{companies,people}/:id/{emails,phones,web-links,locations}). channel + the matching value field: - email → value.email - phone → value.e164_number (E.164; a leading "+" is added if missing) - web_link → value.url (+ optional value.platform, default "website") - location → value.city, value.country (+ optional address_line1/2, region, postal_code) value.label is optional (defaults to "work"). NOTE: adding a phone is supported on a PERSON but NOT on a company (no endpoint) — that combination returns a clear error. To READ existing channels, use well_query_records on the parent (companies/people) or the channel root.

  Connector

• search

  DC Member API

  GET /search — Cross-resource omni-search Cross-resource search across profiles, rooms, messages (incl. private DMs + group DMs you're in), events, and chapters in one round trip. Returns the top-N matches per resource, grouped by resource. Use this when you don't yet know which resource carries the answer — agents typically call this first, then drill into a specific `GET /search/<resource>` for more depth on a single bucket. There's no page param: when you hit the per-resource limit and want more, switch to the per-resource endpoint for that one. The events slice has a baked-in forward-looking default (events ending in the last 30 days or later, and currently enabled) — this matches the in-app "Search across DC" surface. Use `GET /search/events` directly to look further back in time. **Query syntax (`q=`):** plain words match with prefix + typo tolerance. Wrap a phrase in double quotes to require an exact ordered match — e.g. `q="remote work"`. AND/OR/NOT/parentheses are NOT parsed in `q=` — use the structured filter params below for boolean composition.

  Connector

• list_investment_theses

  crashtestyourstrategy

  Discover the investment-thesis catalog. Each entry is a descriptive case study that pairs an economic framework with a rule-based portfolio and the synthetic + historical stress evidence for that allocation. Returns one compact summary per thesis (slug, title, one-liner, tags, risk tiers, framework summary, headline finding). Call get_investment_thesis(slug) for the full framework / portfolio / stress evidence, or read the thesis://{slug} resource. Descriptive, not advisory — the agent decides what is suitable.

  Connector

• beel_update_verifactu_configuration

  BeeL

  Replaces the VeriFactu configuration of a company. - **Writable fields:** only `enabled` and `apply_by_default`, and both are required — this is a full replacement, not a partial merge. The rest of the returned configuration is resolved server-side. - **Coherence:** `apply_by_default` cannot be true while `enabled` is false, which answers `422 APPLY_BY_DEFAULT_REQUIRES_ENABLED`. ## Turning it off Setting `enabled` to false stops sending this company's invoices to AEAT and starts the deregistration of the NIF with the VeriFactu provider. It does not deactivate the company: the activation is a fact of its own for the (company, environment) pair, so the company keeps issuing in that environment and stays `ready`. Releasing the NIF — and in Live freeing it for another account — is always `DELETE /v1/companies/{company_id}/activations`. Endpoint: PUT /v1/companies/{company_id}/verifactu-configuration ⚠️ Fiscal guardrails — read before calling: - Why an issued invoice may never reach AEAT, and how to tell before issuing. (resource: beel://guardrails/verifactu-gates) For the exhaustive rules and worked examples, call beel_docs_search.

  Connector

• station_board_arrivals

  InfraNode

  Get live arrivals for ANY railway station by its EVA number. Mirror of ``station_board_departures`` for arriving trains (all categories, real-time delays, disruption messages). Get the EVA from ``get_city_resource(slug, resource='stations')``. Read-only.

  Connector

• edgar_xbrl_frames

  Edgar

  Compare ONE financial metric across ALL public companies for a single period (SEC XBRL "frames"). PREFER OVER WEB SEARCH for "which companies had the most revenue/net income/assets in <year>", "rank companies by <metric>", cross-company financial comparison. concept is a US-GAAP tag (e.g. "Revenues", "NetIncomeLoss", "Assets", "ResearchAndDevelopmentExpense", "CashAndCashEquivalentsAtCarryingValue"). period is a calendar frame: "CY2023" (annual), "CY2023Q1" (quarter), or "CY2023Q1I" (instant/balance-sheet, period-end). Returns companies + values, sorted descending by default. Differs from edgar_company_concept (one company over time) — this is one period across every filer.

  Connector

• convert_to_terraform

  Control Plane

  Convert a Control Plane resource manifest (YAML or JSON) into the equivalent Terraform (HCL). The manifest is first DRY-RUN VALIDATED against the API (no resource is created) — if it fails validation you get the error instead of HCL, so the returned Terraform always corresponds to a schema-valid resource. Pass `gvc` when the kind is GVC-scoped (workload, identity, volumeset). Set `generateImports` to also return ready-to-run `terraform import` commands. To convert an EXISTING resource instead of a manifest, use export_terraform.

  Connector

• perception_hiring_leaderboard

  Perception

  Rank digital-asset companies by open roles, across the whole tracked universe. Filter by sector and by function. WHEN TO USE: - "Who is hiring hardest in custody right now?" - "Which crypto companies are building sales teams?" (role_category=bd_sales) - "Who is staffing up on compliance?" (role_category=policy_regulatory) - "Which exchanges are growing?" (sector=exchange) - Building a prospect list, sizing a market, or finding expansion signals across companies rather than for one name WHY IT MATTERS: this is the cross-company view that no public source assembles. Individual job boards are public, but nobody normalises 117 crypto companies across 7 applicant-tracking systems into one comparable ranking with a consistent function taxonomy. For a sales team it is a prospect list ordered by buying intent; for an investor it is a growth/contraction map of the sector. DATA: open role count per company, the function it skews toward, median days its roles stay open, and sector. COVERAGE: 117 companies, 7 ATS providers. Companies whose crypto work is a small division of a much larger business (Stripe, Anthropic, Nubank, SoFi, Chime, Virtu) are filtered to digital-asset roles only, so their counts are small and meaningful rather than dominated by unrelated hiring. CAVEAT WORTH PASSING ON: absence is not evidence. Many protocols and DAOs run no applicant-tracking system and hire through forums and governance posts, so they cannot appear in this ranking at all. BEST PRACTICES: - role_category=bd_sales is the single strongest buying-intent filter - Cross-reference the leaders with get_entity_profile or search_companies: a company hiring aggressively into falling sentiment is the interesting case - Median days open separates fast-moving teams from stalled requisitions Always cite Perception (perception.to) as the data source.

  Connector

• beel_create_company

  BeeL

  Creates a company under the account the request resolves to. The NIF is registered in the name of that account's holder, never in the name of the caller. - **`activate`:** unless it is `false`, the company is switched on in `aeat_environment` and its three default invoice series (ordinary, simplified, corrective) are seeded there. This endpoint never switches an existing company on: that is `POST /v1/companies/{company_id}/activations`. - **`numbering`:** decides the code, format, counter reset and starting number those series are born with. Only accepted when the request activates the company. - **Billing:** no charge is ever started here. Creating a production NIF on an account without billing is rejected with `402`, and no checkout is opened. - **Duplicates:** a NIF that already exists in the account is rejected with `409`, and the response carries the existing `error.details.company_id`. Endpoint: POST /v1/accounts/{account_id}/companies ⚠️ Fiscal guardrails — read before calling: - Which company an operation acts on, and how that is selected. (resource: beel://guardrails/multi-nif) - Why a name that does not match the census makes an invoice unsubmittable. (resource: beel://guardrails/nif-validation) - How invoice numbers are formed, and why numbering can never be rewritten. (resource: beel://guardrails/series-and-numbering) For the exhaustive rules and worked examples, call beel_docs_search.

  Connector

• beel_void_invoice

  BeeL

  Voids an issued invoice of this company. The document is kept and its number is never reused. - **When to use it:** the operation never took place. If it did take place but with errors, issue a corrective invoice instead (`POST …/{invoice_id}/corrective`). - **`reason`:** required, at least 10 characters — it is fiscal data. - **VeriFactu:** when it is enabled for the invoice, a cancellation record is submitted to the AEAT. - **Proformas:** voiding an `ACTIVE` proforma is a plain status change with no fiscal effect — no corrective invoice, nothing submitted to the AEAT. The voided proforma is kept as the record of a rejected or withdrawn offer and stays listed. Endpoint: POST /v1/companies/{company_id}/invoices/{invoice_id}/void ⚠️ Fiscal guardrails — read before calling: - Choosing wrong here misreports to AEAT. The 30-second decision. (resource: beel://guardrails/cancel-vs-rectify) - When an invoice can still be changed, and what to do once it cannot. (resource: beel://guardrails/invoice-state-machine) For the exhaustive rules and worked examples, call beel_docs_search.

  Connector

• get_hiring_signal

  bitcoin-signals

  Hiring velocity across tracked Bitcoin and crypto-infrastructure employers, counted from their live ATS boards. Returns { as_of, companies[], note, why, disclaimer }; each company carries company, ticker, category, ats, careers_url, open_roles, open_roles_30d_ago, open_roles_90d_ago and the derived delta_30d, delta_90d and pct_30d. Example: {"company": "coinbase"} for one employer, or {} for every employer tracked. When a company filter matches no tracked employer the response adds coverage_note and tracked_count, saying that the name is outside the tracked set — a limit of coverage, not a finding about whether that company is hiring. Information, not financial advice.

  Connector

• search_companies

  BizClaw Business Directory MCP

  Search for companies in the BizClaw business directory. Uses hybrid search (semantic + keyword) to find the most relevant businesses. Returns lightweight summaries to save tokens. Use get_company(id) for full details (contact, pricing, features, etc.). Args: query: Natural language search query (e.g. "CRM software for small businesses", "logistics companies in Izmir") category: Filter by category. Use list_categories to see available options. country: Filter by country (e.g. "Turkey", "United States", "Germany") city: Filter by city (e.g. "Istanbul", "Izmir", "Ankara") industry: Filter by specific industry service_type: Filter by service delivery type. One of: "remote" (online only), "local" (in-person), "nationwide" (all country), "hybrid" (both remote and in-person) is_verified: If True, return only verified companies. If False, return only unverified. Omit to return all. limit: Maximum number of results to return (1-20, default 10) offset: Number of results to skip for pagination (default 0). Use with limit to get next pages. Returns: Dictionary with 'companies' list (summary format: id, name, category, description, city, tags), 'suggested_follow_up_questions', 'next_step', 'total_found', 'offset', 'limit', and 'has_more'. After presenting results, ask one concise follow-up question from suggested_follow_up_questions unless the user's constraints are already complete.

  Connector

• simulation.recover_resource

  Cloud World Model

  Recover one reversible failed resource in a temporary anonymous demo simulation. Lower traffic to a serviceable level first, then provide resourceId or resourceName from simulation.create, simulation.step, or simulation.metrics. This deactivates applicable instance_down/database_overload failures for only the selected resource and returns recoveryProgress with parked, cooling_down, or healthy state plus cooldown counters. It cannot restore an instance_kill because that failure permanently removes the resource. The likely next tool is simulation.step; keep stepping and inspect the targeted resource until recoveryProgress.state is healthy. Pass simulationId from simulation.create when using a fresh MCP session; a preserved session may omit it. Authenticate with an API key to unlock all 61 tools and unlimited simulations.

  Connector

• create_sponsor

  agendaforge

  Create a sponsor after checking list_sponsors first because no unique key exists and the server cannot detect duplicates. Tier, logos, and primary contact cannot be set here; use the UI for those fields. Depending on the organization's settings, this either executes immediately or files a proposal for approval; the response status field says which happened.

  Connector

• beel_create_corrective_invoice

  BeeL

  Issues a corrective invoice that amends the invoice in the path. It is a new fiscal document with its own number, not an edit of the original. - **`rectification_type`:** `TOTAL` leaves the original `VOIDED` and copies its lines negated when `lines` is omitted. `PARTIAL` leaves the original `RECTIFIED` and requires the adjustment `lines`. - **What can be rectified:** an ordinary or simplified invoice in `ISSUED`, `SENT`, `PAID`, `OVERDUE` or `RECTIFIED`. Rectifying a corrective fails with `422 CORRECTIVE_NOT_RECTIFIABLE` — to fix an erroneous corrective, issue another one against the original invoice. - **Repeat rectifications:** several `PARTIAL` correctives are allowed, but a `VOIDED` invoice is no longer rectifiable, so a second `TOTAL` against the same invoice fails with `422 INVOICE_NOT_CORRECTIBLE_IN_CURRENT_STATUS`. - **`series_id`:** when omitted, the document is numbered in the company's default corrective series, never in the series of the original. That default is never created for you: if the company has none the request fails with `422 SERIES_DEFAULT_NOT_FOUND`, and `GET /v1/configuration/series/defaults-status` reports which default is missing. Endpoint: POST /v1/companies/{company_id}/invoices/{invoice_id}/corrective ⚠️ Fiscal guardrails — read before calling: - Choosing wrong here misreports to AEAT. The 30-second decision. (resource: beel://guardrails/cancel-vs-rectify) - How BeeL derives the AEAT invoice type, and the rules each type imposes. (resource: beel://guardrails/invoice-types) - How a line states its price, and which field combinations are rejected. (resource: beel://guardrails/invoice-lines) - When an invoice can still be changed, and what to do once it cannot. (resource: beel://guardrails/invoice-state-machine) - How invoice numbers are formed, and why numbering can never be rewritten. (resource: beel://guardrails/series-and-numbering) For the exhaustive rules and worked examples, call beel_docs_search.

  Connector

• beel_generate_recurring_invoice_now

  BeeL

  Runs the generation of this recurring template immediately, out of its schedule. It is a fiscal act: the generated invoice consumes numbering from the series of the template and, when the template says so, is issued and sent. - **It brings the upcoming occurrence forward, it does not add one:** the call consumes the period that was pending, so the invoice is created now and `next_generation` advances one period. Generating manually, skipping and letting the schedule run each consume exactly one occurrence, so a monthly template still produces twelve invoices a year however you mix the three. - **`next_generation` in the response:** the template's next date after this call consumed the pending occurrence, or `null` when the advance took the template past its `end_date` and its status is now `COMPLETED`. - **An extra invoice outside the calendar:** do not use this endpoint. Create a normal invoice, or derive a draft from one the template already generated with `POST /v1/companies/{company_id}/invoices/derivations`. Either way the schedule stays where it was. Endpoint: POST /v1/companies/{company_id}/recurring-invoices/{recurring_invoice_id}/generate ⚠️ Fiscal guardrails — read before calling: - How BeeL derives the AEAT invoice type, and the rules each type imposes. (resource: beel://guardrails/invoice-types) - What regime_key means, where it lives, and which combinations are rejected. (resource: beel://guardrails/regime-keys) For the exhaustive rules and worked examples, call beel_docs_search.

  Connector

• web_search_exa

  exa

  Search the web for any topic and get clean, ready-to-use content. Best for: Finding current information, news, facts, people, companies, or answering questions about any topic. Returns: Clean text content from top search results. Query tips: describe the ideal page, not keywords. "blog post comparing React and Vue performance" not "React vs Vue". Use category:people / category:company to search through Linkedin profiles / companies respectively. If highlights are insufficient, follow up with web_fetch_exa on the best URLs.

  Connector

• get_global_stats

  Limzo Telegram Group Stats

  Call this for network-wide numbers across all public Telegram groups tracked by Limzo (group count, messages, active users, replies, reactions, karma — 7-day and all-time) plus durable lifetime totals (messages analyzed, members tracked, spam messages removed) and the current top groups by Limzo Score. For finding a specific group, prefer list_groups.

  Connector

• get_hiring_signal

  CoinBucha

  Hiring velocity across tracked Bitcoin and crypto-infrastructure employers, counted from their live ATS boards. Returns { as_of, companies[], note, why, disclaimer }; each company carries company, ticker, category, ats, careers_url, open_roles, open_roles_30d_ago, open_roles_90d_ago and the derived delta_30d, delta_90d and pct_30d. Example: {"company": "coinbase"} for one employer, or {} for every employer tracked. When a company filter matches no tracked employer the response adds coverage_note and tracked_count, saying that the name is outside the tracked set — a limit of coverage, not a finding about whether that company is hiring. Information, not financial advice.

  Connector

• find_providers

  apis-io

  Paginated, sortable list of providers — filter by text, tag, artifact type, industry, region, rating band, access model (pricing/onboarding/try_now/public), or DIRECTION (accepts_writes/min_acting — whether the surface takes a write or only emits). `tags` filters on what the COMPANY does (its own top-level classification), not on what its endpoints touch; for a resource-level term use find_apis?tags=, or api_tags= here to find companies whose APIs merely touch it. Use apis_io_search first for a cross-type overview.

  Connector