"Tools and methods to automate PC interactions" matching MCP tools:

• invoke_mtprotoA

  Fast MCP TelegramA

  Low-level Telegram API (MTProto) invoke for methods not wrapped by other tools. Dangerous methods require allow_dangerous=true. Success: API result dict or normalized error. PII and credential-shaped fields (phone, access_hash) are dropped from a successful result by default; pass include_sensitive=true for the raw payload. A bare message id needs a chat binding: requests with no peer field (messages.GetMessages, messages.DeleteMessages) are refused, because a bare id resolves against an arbitrary dialog. Use channels.GetMessages or messages.GetHistory, which carry the binding. messages.GetHistory cannot address a forum topic (no thread_id/top_msg_id in the schema, and channels.GetHistory does not exist) -- use messages.Search with top_msg_id, or the high-level get_messages with reply_to_id. Full documentation: https://github.com/leshchenko1979/fast-mcp-telegram/blob/main/docs/Tools-Reference.md

  Connector

  Destructive

  No auth

• invoke_mtprotoA

  fast-mcp-telegramA

  Low-level Telegram API (MTProto) invoke for methods not wrapped by other tools. Dangerous methods require allow_dangerous=true. Success: API result dict or normalized error. PII and credential-shaped fields (phone, access_hash) are dropped from a successful result by default; pass include_sensitive=true for the raw payload. A bare message id needs a chat binding: requests with no peer field (messages.GetMessages, messages.DeleteMessages) are refused, because a bare id resolves against an arbitrary dialog. Use channels.GetMessages or messages.GetHistory, which carry the binding. messages.GetHistory cannot address a forum topic (no thread_id/top_msg_id in the schema, and channels.GetHistory does not exist) -- use messages.Search with top_msg_id, or the high-level get_messages with reply_to_id. Full documentation: https://github.com/leshchenko1979/fast-mcp-telegram/blob/main/docs/Tools-Reference.md

  Connector

  Destructive

  No auth

• scaffold_serviceA

  @imqueueA

  READ-ONLY: returns generated source code as text and writes nothing to disk, creates no project and runs no command. Generates an idiomatic @imqueue/rpc service (an IMQService subclass with @expose()d, JSDoc-typed methods) plus a bootstrap that starts it. Provide the methods you want, or omit them for a starter template. Any non-primitive parameter or return type also gets a types.ts with the required @classType()/@property() declarations — without those the generated client types it `any`, which compiles. Use create_service (local install only) if you want files actually written.

  ConnectorNo auth

• depreciation_calculatorA

  Calculate.co.nz NZ CalculatorsA

  Depreciate an asset by straight line or diminishing value, with a year by year schedule. Use for: 'how is depreciation calculated', 'straight line vs diminishing value', 'depreciation schedule', 'book value after 3 years', 'work out depreciation on equipment'. THE TWO METHODS DIVERGE SHARPLY ON THE SAME ASSET. Straight line spreads the deduction evenly across the useful life. Diminishing value applies the rate to the REDUCING book value, so it front-loads the deduction heavily and never reaches zero on its own. Which is better depends entirely on when the owner wants the deduction, so the year by year schedule is the useful part of this answer rather than the first year figure. Show the schedule. additional_costs are capitalised into the cost base, which is where delivery and installation belong. salvage_value acts as a floor under both methods, and the last year of a straight line life takes only what is left, so rounding cannot push the book value below it. ONE IMPORTANT LIMIT, AND IT MATTERS. This is the ARITHMETIC of the two methods on a rate you supply. It is NOT a lookup of Inland Revenue's prescribed rates, which vary by asset class and are published in the IRD depreciation rate finder. If someone needs to know the right RATE for a particular asset, send them to that finder. DO NOT INVENT A RATE to feed this tool and present the output as their tax position. Args: initial_cost: Purchase price of the asset. method: straight_line or diminishing_value. additional_costs: Costs capitalised in, such as delivery or installation. salvage_value: Expected residual value. A floor under both methods. useful_life_years: Years of life. Required for straight line. annual_rate_pct: Rate per year. Required for diminishing value. years_to_schedule: Years to show. Defaults to the life, or ten. Returns: The cost base, the depreciable amount, the first year charge, the total charged, the closing book value and the full year by year schedule.

  ConnectorNo auth

• rpc_callA

  BlockVectra: multi-chain RPC & Data APIA

  Execute a read-only JSON-RPC 2.0 method on a specified blockchain network using your BlockVectra API key, or via the keyless public endpoint if available on the chain. Chain slugs look like 'base_mainnet'; take them from list_chains. Without a key the call goes to the keyless endpoint `/v1/{chain}/public` (the chain's `public.url` in list_chains), which only serves the methods listed in that chain's `public.methods`. Write methods (such as 'eth_sendRawTransaction') are not supported in rpc_call; use 'send_raw_transaction' instead. Consult the Ethereum JSON-RPC specification (https://ethereum.org/en/developers/docs/apis/json-rpc/) and the BlockVectra method reference (https://docs.blockvectra.com/en/api/json-rpc/methods/). With a key, set the 'x-api-key' or 'Authorization: Bearer <key>' HTTP header in your MCP client configuration for full access (keys must not be passed in tool parameters or chat). Returns the raw JSON-RPC response from the server.

  ConnectorNo auth

• awareness_apply_skillA

  Awareness — Memory, Knowledge & Agent MarketsA

  Apply a learned skill — returns structured step-by-step execution plan. Call this when a task matches an active skill from awareness_init's active_skills. Returns the skill's methods, summary, and context-adapted guidance. Automatically marks the skill as used (resets decay timer). Args: skill_id: ID of the skill to apply (from active_skills). context: Current task context — the execution plan will be adapted to this. memory_id: Target memory id (auto-resolved if omitted). api_key: Bearer token for authentication.

  ConnectorNo auth

• get_supplement_infoA

  Aviado Health BioIntelligenceA

  Overview of one supplement: description, typical uses, its top 5 biomarkers (with up to 3 PubMed citations each), goals, mechanism tags and cited safety contraindications. Contraindications include those recorded for what it contains (e.g. turmeric shows curcumin's), labelled with recorded_for; only cited rows are shown, so an empty list is not proof of safety. For all biomarkers use get_biomarkers_for_supplement; for drug interactions use get_supplement_interactions. The supplement may be a name or an Aviado canonical_id (from search_supplements or a candidates list). Check status first: needs_confirmation / no_match means the input did not resolve, data is null and next_step says how to retry.

  ConnectorNo auth

• get_billing_portalA

  BorealHostB

  Get a Stripe billing portal URL for managing payment methods and invoices. Returns a URL (not a redirect) that the human can open in a browser. Requires: API key with read scope. Args: flow: Optional. Set to "payment_method_update" to go directly to the payment method update page. Returns: {"url": "https://billing.stripe.com/p/session/..."}

  ConnectorNo auth

• update_live_flowA

  Power Automate MCP Server by Flow StudioA

  Update or create a flow. Use `dryRun: true` to preview any change without writing. Omit flowName to create: definition and displayName are required. Give flowName to update: displayName and/or definition and/or connectionReferences. SURGICAL EDIT: pass `operations` — an ordered list of set/add/remove/merge ops on array-of-keys paths — to change one action or parameter without resending the whole definition. Provide EITHER operations OR definition; connectionReferences may accompany either and lands in the same save. WHOLE definition: call get_live_flow, mutate properties.definition, pass it here. RENAME: pass displayName alone. Power Automate rejects a PATCH carrying no flow content, so this re-saves the unchanged definition — the maker portal does the same. definition.description is required, and must be brief — we append " #flowstudio-mcp" to it.

  Connector

  Destructive

  No auth

• compute_utility_chamberA

  civilquantsA

  Paid tier only. Calling this without an authenticated CivilQuants account returns TIER_INSUFFICIENT — sign up at https://civilquants.com/pricing or use the free-tier alternative compute_manhole. Catalogue-driven utility access chamber covering ten standard UK types: BT/Openreach jointing chambers JC1-JC4 (defaulting to UTILITY_PROVIDER_SUPPLY routing), water meter chamber (FW6), wastewater inspection chamber (RW9), valve chamber, gas Emergency Control Valve pit (ECV), LV electrical link box, and cable draw pit. Composite emission: precast chamber unit + BS EN 124 cover & frame (PC supply) + excavation + bedding (SHW Cl. 803) + granular surround + optional geotextile + selected fill + disposal. Routes via manhole_type=utility_chamber attribute discrimination through CESMM4 Class K.1.5.x, NRM2 33.7.11-.13, MMHW 500.5.13-.15 (SHW Cl. 507), and SMM7 R12.3.10-.12. JC types route their chamber unit through the v18 statutory-undertaker supply route infrastructure (CESMM4 Class A.4.3, NRM2 Group 1, MMHW Series 100, SMM7 A53) as a PC sum plus contractor attendance line. Example params: bedding_thickness_mm=150 mm (75–300), bedding_overhang_m=0.1 m (0.075–0.3), surround_thickness_m=0.15 m (0.1–0.3). Example call: {"params": {"bedding_thickness_mm": 150, "bedding_overhang_m": 0.1, "surround_thickness_m": 0.15}, "standard": "MMHW"}. Omitted parameters use sensible engineering defaults. Pass deliverables=["xlsx","dxf","pdf"] (any subset) to also receive one-shot download URLs in the same call: Excel BoQ (both tiers, watermarked free) plus the dimensioned DXF (CAD) and PDF drawing sheets (paid tier).

  ConnectorNo auth

• get_supplement_infoA

  Aviado AIA

  Overview of one supplement: description, typical uses, its top 5 biomarkers (with up to 3 PubMed citations each), goals, mechanism tags and cited safety contraindications. Contraindications include those recorded for what it contains (e.g. turmeric shows curcumin's), labelled with recorded_for; only cited rows are shown, so an empty list is not proof of safety. For all biomarkers use get_biomarkers_for_supplement; for drug interactions use get_supplement_interactions. The supplement may be a name or an Aviado canonical_id (from search_supplements or a candidates list). Check status first: needs_confirmation / no_match means the input did not resolve, data is null and next_step says how to retry.

  ConnectorNo auth

• federation_whyA

  ComOS Federation GatewayA

  Why build on ComOS — the case for becoming a vendor, not just a buyer. federation_help tells you HOW; this tells you WHY. Read this if you (or your human) are deciding whether to invest a few Coms to stand up a business. Returns the thesis: arrive with a small float, leave running a vertically-integrated operation that buys from vendor-agents, sells to customer-agents, automates the loop, and compounds — relayable verbatim to the human root who controls the funds. Returns: A thesis object: the becoming-thesis, the play (buy/sell/automate/compound/integrate), what-you-could-become, why-it-compounds, the quoted economics, the honest door-state caveat (open via tokened apply; tokenless never admits), and pointers to federation_help / how-to / the on-ramp manifest. Example: call federation_why with arguments {}.

  ConnectorNo auth

• federation_enter_tenantA

  ComOS Federation GatewayA

  Enter a tenant to receive its tool surface (progressive disclosure). The gateway is a small catalog — list tenants with federation_list_tenants, then enter one here. The reply is authoritative: platform_tools / platform_tool_defs carry the entered platform's REAL action tools with descriptions and schemas (e.g. retail → catalog_search / order_create; bookings → services_search / booking_hold); composed_tool_defs carries its knowledge tools. Your session persists by the mcp-session-id header (echoed on every response; idle sessions expire after 24h — re-enter to resume): after entering, branched tools are callable with ordinary MCP tools/call on this session and appear in its tools/list; re-entering re-scopes. REST twin: POST /tools/<name> on this host, JSON body = the tool's arguments plus {"tenant_id":"<entered tenant>"}, with your Authorization header for scoped tools. Info tenants (about-us, how-to) serve read-only knowledge directly on tools/list. Returns: { platform_tools: [...] } — the authoritative tool list branched onto your session for that tenant. Example: call federation_enter_tenant with arguments {"tenant_id":"<tenant_id>"}.

  ConnectorNo auth

• federation_whyA

  ComOS FederationA

  Why build on ComOS — the case for becoming a vendor, not just a buyer. federation_help tells you HOW; this tells you WHY. Read this if you (or your human) are deciding whether to invest a few Coms to stand up a business. Returns the thesis: arrive with a small float, leave running a vertically-integrated operation that buys from vendor-agents, sells to customer-agents, automates the loop, and compounds — relayable verbatim to the human root who controls the funds. Returns: A thesis object: the becoming-thesis, the play (buy/sell/automate/compound/integrate), what-you-could-become, why-it-compounds, the quoted economics, the honest door-state caveat (open via tokened apply; tokenless never admits), and pointers to federation_help / how-to / the on-ramp manifest. Example: call federation_why with arguments {}.

  ConnectorNo auth

• federation_enter_tenantA

  ComOS FederationA

  Enter a tenant to receive its tool surface (progressive disclosure). The gateway is a small catalog — list tenants with federation_list_tenants, then enter one here. The reply is authoritative: platform_tools / platform_tool_defs carry the entered platform's REAL action tools with descriptions and schemas (e.g. retail → catalog_search / order_create; bookings → services_search / booking_hold); composed_tool_defs carries its knowledge tools. Your session persists by the mcp-session-id header (echoed on every response; idle sessions expire after 24h — re-enter to resume): after entering, branched tools are callable with ordinary MCP tools/call on this session and appear in its tools/list; re-entering re-scopes. REST twin: POST /tools/<name> on this host, JSON body = the tool's arguments plus {"tenant_id":"<entered tenant>"}, with your Authorization header for scoped tools. Info tenants (about-us, how-to) serve read-only knowledge directly on tools/list. Returns: { platform_tools: [...] } — the authoritative tool list branched onto your session for that tenant. Example: call federation_enter_tenant with arguments {"tenant_id":"<tenant_id>"}.

  ConnectorNo auth

• federation_whyA

  ComOS Federation GatewayA

  Why build on ComOS — the case for becoming a vendor, not just a buyer. federation_help tells you HOW; this tells you WHY. Read this if you (or your human) are deciding whether to invest a few Coms to stand up a business. Returns the thesis: arrive with a small float, leave running a vertically-integrated operation that buys from vendor-agents, sells to customer-agents, automates the loop, and compounds — relayable verbatim to the human root who controls the funds. Returns: A thesis object: the becoming-thesis, the play (buy/sell/automate/compound/integrate), what-you-could-become, why-it-compounds, the quoted economics, the honest door-state caveat (open via tokened apply; tokenless never admits), and pointers to federation_help / how-to / the on-ramp manifest. Example: call federation_why with arguments {}.

  ConnectorNo auth

• federation_enter_tenantA

  ComOS Federation GatewayA

  Enter a tenant to receive its tool surface (progressive disclosure). The gateway is a small catalog — list tenants with federation_list_tenants, then enter one here. The reply is authoritative: platform_tools / platform_tool_defs carry the entered platform's REAL action tools with descriptions and schemas (e.g. retail → catalog_search / order_create; bookings → services_search / booking_hold); composed_tool_defs carries its knowledge tools. Your session persists by the mcp-session-id header (echoed on every response; idle sessions expire after 24h — re-enter to resume): after entering, branched tools are callable with ordinary MCP tools/call on this session and appear in its tools/list; re-entering re-scopes. REST twin: POST /tools/<name> on this host, JSON body = the tool's arguments plus {"tenant_id":"<entered tenant>"}, with your Authorization header for scoped tools. Info tenants (about-us, how-to) serve read-only knowledge directly on tools/list. Returns: { platform_tools: [...] } — the authoritative tool list branched onto your session for that tenant. Example: call federation_enter_tenant with arguments {"tenant_id":"<tenant_id>"}.

  ConnectorNo auth

• recommend_toolsA

  RightAIChoice — verified AI tool dataA

  Use this when the user describes what they need an AI tool to DO rather than naming one — "something to transcribe interviews", "an image generator with an API", "a writing tool for a small team". Returns a verified shortlist matched on the described need, filtered by constraints the caller sets, and — unique to this catalog — screened against a survival bar: tools failing our link-health probes or scoring badly on the 5-signal viability model can be excluded outright. Each result carries its own health verdict, the date our record of it was last rebuilt, and pricing model. Matching combines meaning-based search (text embeddings of each listing) with keyword search over 8,000+ verified tools; the response states which methods ran. Tools with no viability measurement yet are listed separately by name rather than silently dropped. Not for: questions about a tool the user already named (use check_tool_status), head-to-head choices (use compare_tools), or filtering by price amount — prices are recorded verbatim in mixed currencies and are never converted or compared numerically.

  ConnectorNo auth

• recommend_toolsA

  RightAIChoiceA

  Use this when the user describes what they need an AI tool to DO rather than naming one — "something to transcribe interviews", "an image generator with an API", "a writing tool for a small team". Returns a verified shortlist matched on the described need, filtered by constraints the caller sets, and — unique to this catalog — screened against a survival bar: tools failing our link-health probes or scoring badly on the 5-signal viability model can be excluded outright. Each result carries its own health verdict, the date our record of it was last rebuilt, and pricing model. Matching combines meaning-based search (text embeddings of each listing) with keyword search over 8,000+ verified tools; the response states which methods ran. Tools with no viability measurement yet are listed separately by name rather than silently dropped. Not for: questions about a tool the user already named (use check_tool_status), head-to-head choices (use compare_tools), or filtering by price amount — prices are recorded verbatim in mixed currencies and are never converted or compared numerically.

  ConnectorNo auth

• update_auth_methodsA

  The BridgeA

  Toggle the app's login methods. Only the fields you pass are changed: mfaEnabled (MFA as a second factor), passkeysEnabled (WebAuthn passkeys), magicLinkEnabled (email magic links), and the social provider flags (googleSsoEnabled, linkedinSsoEnabled, azureAdSsoEnabled, appleSsoEnabled, githubSsoEnabled, facebookSsoEnabled). Email + password login is always available on Bridge and has no toggle. A social provider can only be switched on once its credentials are saved — otherwise Bridge refuses with SIGN_IN_CREDENTIALS_MISSING and a fix; to configure a provider end-to-end (credentials + enable + callback URL) use setup_sso. Bridge also refuses to switch off the last remaining sign-in method (LAST_SIGN_IN_METHOD). CLI: `bridge auth methods enable|disable <method>`. Returns the updated login-method configuration (same projection as get_auth_config). For MFA this is the same as `bridge auth mfa --enabled true|false`. Before writing app code that consumes this, call get_integration_guide with topic=auth and the framework the app uses.

  ConnectorOAuth

• broker_sync_prop_firmsA

  Wicked MCPA

  [Broker Sync API] Prop-firm platform integration registry — live-verified methods (Topstep ProjectX API, FTMO MatchTrader bridge) and connection status. Use when you want the registry of prop-firm platforms and which integration methods are live-verified. Not for a user's own accounts (use broker_sync_connections). Behavior: read-only. Priced via x402 (USDC on Base) or free with WICKEDAPI_API_KEY; with neither, you get HTTP 402 with the decoded price in payment_required (a price quote, not a failure).

  ConnectorNo auth