Toolpin

Tool index

pipeworx_feedback

Exposed by 1312 servers, with 2 different definitions behind the one name.

The same name does not mean the same tool here.

1312 servers expose pipeworx_feedback and we have recorded 2 distinct definitions of it. Compare the parameters below before assuming one is a drop-in for another.

io.github.pipeworx-io/cheapshark reachable

PC game deals across Steam/Epic/GOG/Humble via CheapShark. Keyless.

Send Pipeworx Feedback

Tell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). ONLY for tools served by this Pipeworx connection — if the tool came from a different MCP server in your client (another vendor's Gmail, Splunk, Slack, etc. connector), we cannot fix it and reporting it here only delays you; file it with that server instead. Not sure? Pipeworx tool names are the ones this connection lists. Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt. Filing without an account returns a `claim_token`; pass it back later as pipeworx_feedback({claim_token:"pwfb_…"}) to read whether it was fixed and what changed. The team reads digests daily and signal directly affects roadmap. Rate-limited to 5 per identifier per day. Free; doesn't count against your tool-call quota.

ParameterTypeDescription
type string bug = something broke or returned wrong data. feature = a new tool or capability you wish existed. data_gap = data Pipeworx does not currently expose. praise = positive note. other = anything else.
one of: bug, feature, data_gap, praise, other
context object Optional structured context: which tool, pack, or vertical this relates to.
message string Your feedback in plain text. Be specific (which tool, what error, what data was missing). 1-2 sentences typical, 2000 chars max.
claim_token string Read the reply to a report you filed earlier: pass the `pwfb_…` token that filing returned, with no other arguments. Returns the status and, once resolved, what actually changed.

* required

Author's annotations: readOnlyHint=False, openWorldHint=False, idempotentHint=False, destructiveHint=False. These are claims by whoever wrote the server, not something we verified.

no output schema sha256 9d964bf5d4347fc5 read 2026-08-27 repository
io.github.pipeworx-io/chembl reachable

ChEMBL MCP — drug discovery database (EBI).

Send Pipeworx Feedback

Tell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). ONLY for tools served by this Pipeworx connection — if the tool came from a different MCP server in your client (another vendor's Gmail, Splunk, Slack, etc. connector), we cannot fix it and reporting it here only delays you; file it with that server instead. Not sure? Pipeworx tool names are the ones this connection lists. Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt. Filing without an account returns a `claim_token`; pass it back later as pipeworx_feedback({claim_token:"pwfb_…"}) to read whether it was fixed and what changed. The team reads digests daily and signal directly affects roadmap. Rate-limited to 5 per identifier per day. Free; doesn't count against your tool-call quota.

ParameterTypeDescription
type string bug = something broke or returned wrong data. feature = a new tool or capability you wish existed. data_gap = data Pipeworx does not currently expose. praise = positive note. other = anything else.
one of: bug, feature, data_gap, praise, other
context object Optional structured context: which tool, pack, or vertical this relates to.
message string Your feedback in plain text. Be specific (which tool, what error, what data was missing). 1-2 sentences typical, 2000 chars max.
claim_token string Read the reply to a report you filed earlier: pass the `pwfb_…` token that filing returned, with no other arguments. Returns the status and, once resolved, what actually changed.

* required

Author's annotations: readOnlyHint=False, openWorldHint=False, idempotentHint=False, destructiveHint=False. These are claims by whoever wrote the server, not something we verified.

no output schema sha256 9d964bf5d4347fc5 read 2026-08-27 repository
io.github.pipeworx-io/chess reachable

Chess.com MCP — wraps the Chess.com public API (free, no auth)

Send Pipeworx Feedback

Tell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). ONLY for tools served by this Pipeworx connection — if the tool came from a different MCP server in your client (another vendor's Gmail, Splunk, Slack, etc. connector), we cannot fix it and reporting it here only delays you; file it with that server instead. Not sure? Pipeworx tool names are the ones this connection lists. Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt. Filing without an account returns a `claim_token`; pass it back later as pipeworx_feedback({claim_token:"pwfb_…"}) to read whether it was fixed and what changed. The team reads digests daily and signal directly affects roadmap. Rate-limited to 5 per identifier per day. Free; doesn't count against your tool-call quota.

ParameterTypeDescription
type string bug = something broke or returned wrong data. feature = a new tool or capability you wish existed. data_gap = data Pipeworx does not currently expose. praise = positive note. other = anything else.
one of: bug, feature, data_gap, praise, other
context object Optional structured context: which tool, pack, or vertical this relates to.
message string Your feedback in plain text. Be specific (which tool, what error, what data was missing). 1-2 sentences typical, 2000 chars max.
claim_token string Read the reply to a report you filed earlier: pass the `pwfb_…` token that filing returned, with no other arguments. Returns the status and, once resolved, what actually changed.

* required

Author's annotations: readOnlyHint=False, openWorldHint=False, idempotentHint=False, destructiveHint=False. These are claims by whoever wrote the server, not something we verified.

no output schema sha256 9d964bf5d4347fc5 read 2026-08-27 repository
io.github.pipeworx-io/chile-procurement reachable

Chile Government Procurement MCP — Mercado Público / ChileCompra (keyless-ish).

Send Pipeworx Feedback

Tell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). ONLY for tools served by this Pipeworx connection — if the tool came from a different MCP server in your client (another vendor's Gmail, Splunk, Slack, etc. connector), we cannot fix it and reporting it here only delays you; file it with that server instead. Not sure? Pipeworx tool names are the ones this connection lists. Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt. Filing without an account returns a `claim_token`; pass it back later as pipeworx_feedback({claim_token:"pwfb_…"}) to read whether it was fixed and what changed. The team reads digests daily and signal directly affects roadmap. Rate-limited to 5 per identifier per day. Free; doesn't count against your tool-call quota.

ParameterTypeDescription
type string bug = something broke or returned wrong data. feature = a new tool or capability you wish existed. data_gap = data Pipeworx does not currently expose. praise = positive note. other = anything else.
one of: bug, feature, data_gap, praise, other
context object Optional structured context: which tool, pack, or vertical this relates to.
message string Your feedback in plain text. Be specific (which tool, what error, what data was missing). 1-2 sentences typical, 2000 chars max.
claim_token string Read the reply to a report you filed earlier: pass the `pwfb_…` token that filing returned, with no other arguments. Returns the status and, once resolved, what actually changed.

* required

Author's annotations: readOnlyHint=False, openWorldHint=False, idempotentHint=False, destructiveHint=False. These are claims by whoever wrote the server, not something we verified.

no output schema sha256 9d964bf5d4347fc5 read 2026-08-27 repository
io.github.pipeworx-io/china-stocks reachable

China A-shares MCP. Keyless.

Send Pipeworx Feedback

Tell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). ONLY for tools served by this Pipeworx connection — if the tool came from a different MCP server in your client (another vendor's Gmail, Splunk, Slack, etc. connector), we cannot fix it and reporting it here only delays you; file it with that server instead. Not sure? Pipeworx tool names are the ones this connection lists. Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt. Filing without an account returns a `claim_token`; pass it back later as pipeworx_feedback({claim_token:"pwfb_…"}) to read whether it was fixed and what changed. The team reads digests daily and signal directly affects roadmap. Rate-limited to 5 per identifier per day. Free; doesn't count against your tool-call quota.

ParameterTypeDescription
type string bug = something broke or returned wrong data. feature = a new tool or capability you wish existed. data_gap = data Pipeworx does not currently expose. praise = positive note. other = anything else.
one of: bug, feature, data_gap, praise, other
context object Optional structured context: which tool, pack, or vertical this relates to.
message string Your feedback in plain text. Be specific (which tool, what error, what data was missing). 1-2 sentences typical, 2000 chars max.
claim_token string Read the reply to a report you filed earlier: pass the `pwfb_…` token that filing returned, with no other arguments. Returns the status and, once resolved, what actually changed.

* required

Author's annotations: readOnlyHint=False, openWorldHint=False, idempotentHint=False, destructiveHint=False. These are claims by whoever wrote the server, not something we verified.

no output schema sha256 9d964bf5d4347fc5 read 2026-08-27 repository
io.github.pipeworx-io/chucknorris reachable

Chuck Norris MCP — wraps chucknorris.io (free, no auth)

Send Pipeworx Feedback

Tell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). ONLY for tools served by this Pipeworx connection — if the tool came from a different MCP server in your client (another vendor's Gmail, Splunk, Slack, etc. connector), we cannot fix it and reporting it here only delays you; file it with that server instead. Not sure? Pipeworx tool names are the ones this connection lists. Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt. Filing without an account returns a `claim_token`; pass it back later as pipeworx_feedback({claim_token:"pwfb_…"}) to read whether it was fixed and what changed. The team reads digests daily and signal directly affects roadmap. Rate-limited to 5 per identifier per day. Free; doesn't count against your tool-call quota.

ParameterTypeDescription
type string bug = something broke or returned wrong data. feature = a new tool or capability you wish existed. data_gap = data Pipeworx does not currently expose. praise = positive note. other = anything else.
one of: bug, feature, data_gap, praise, other
context object Optional structured context: which tool, pack, or vertical this relates to.
message string Your feedback in plain text. Be specific (which tool, what error, what data was missing). 1-2 sentences typical, 2000 chars max.
claim_token string Read the reply to a report you filed earlier: pass the `pwfb_…` token that filing returned, with no other arguments. Returns the status and, once resolved, what actually changed.

* required

Author's annotations: readOnlyHint=False, openWorldHint=False, idempotentHint=False, destructiveHint=False. These are claims by whoever wrote the server, not something we verified.

no output schema sha256 9d964bf5d4347fc5 read 2026-08-27 repository
io.github.pipeworx-io/cisa-kev error

CISA Known Exploited Vulnerabilities catalog

Send Pipeworx Feedback

Tell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt. The team reads digests daily and signal directly affects roadmap. Rate-limited to 5 per identifier per day. Free; doesn't count against your tool-call quota.

ParameterTypeDescription
type* string bug = something broke or returned wrong data. feature = a new tool or capability you wish existed. data_gap = data Pipeworx does not currently expose. praise = positive note. other = anything else.
one of: bug, feature, data_gap, praise, other
context object Optional structured context: which tool, pack, or vertical this relates to.
message* string Your feedback in plain text. Be specific (which tool, what error, what data was missing). 1-2 sentences typical, 2000 chars max.

* required

Author's annotations: readOnlyHint=False, openWorldHint=False, idempotentHint=False, destructiveHint=False. These are claims by whoever wrote the server, not something we verified.

no output schema sha256 e29cd1191b879e4d read 2026-07-29 repository
io.github.pipeworx-io/citybikes reachable

Citybikes MCP — wraps CityBik.es API (free, no auth required)

Send Pipeworx Feedback

Tell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). ONLY for tools served by this Pipeworx connection — if the tool came from a different MCP server in your client (another vendor's Gmail, Splunk, Slack, etc. connector), we cannot fix it and reporting it here only delays you; file it with that server instead. Not sure? Pipeworx tool names are the ones this connection lists. Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt. Filing without an account returns a `claim_token`; pass it back later as pipeworx_feedback({claim_token:"pwfb_…"}) to read whether it was fixed and what changed. The team reads digests daily and signal directly affects roadmap. Rate-limited to 5 per identifier per day. Free; doesn't count against your tool-call quota.

ParameterTypeDescription
type string bug = something broke or returned wrong data. feature = a new tool or capability you wish existed. data_gap = data Pipeworx does not currently expose. praise = positive note. other = anything else.
one of: bug, feature, data_gap, praise, other
context object Optional structured context: which tool, pack, or vertical this relates to.
message string Your feedback in plain text. Be specific (which tool, what error, what data was missing). 1-2 sentences typical, 2000 chars max.
claim_token string Read the reply to a report you filed earlier: pass the `pwfb_…` token that filing returned, with no other arguments. Returns the status and, once resolved, what actually changed.

* required

Author's annotations: readOnlyHint=False, openWorldHint=False, idempotentHint=False, destructiveHint=False. These are claims by whoever wrote the server, not something we verified.

no output schema sha256 9d964bf5d4347fc5 read 2026-08-27 repository
io.github.pipeworx-io/civitai reachable

Civitai MCP.

Send Pipeworx Feedback

Tell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). ONLY for tools served by this Pipeworx connection — if the tool came from a different MCP server in your client (another vendor's Gmail, Splunk, Slack, etc. connector), we cannot fix it and reporting it here only delays you; file it with that server instead. Not sure? Pipeworx tool names are the ones this connection lists. Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt. Filing without an account returns a `claim_token`; pass it back later as pipeworx_feedback({claim_token:"pwfb_…"}) to read whether it was fixed and what changed. The team reads digests daily and signal directly affects roadmap. Rate-limited to 5 per identifier per day. Free; doesn't count against your tool-call quota.

ParameterTypeDescription
type string bug = something broke or returned wrong data. feature = a new tool or capability you wish existed. data_gap = data Pipeworx does not currently expose. praise = positive note. other = anything else.
one of: bug, feature, data_gap, praise, other
context object Optional structured context: which tool, pack, or vertical this relates to.
message string Your feedback in plain text. Be specific (which tool, what error, what data was missing). 1-2 sentences typical, 2000 chars max.
claim_token string Read the reply to a report you filed earlier: pass the `pwfb_…` token that filing returned, with no other arguments. Returns the status and, once resolved, what actually changed.

* required

Author's annotations: readOnlyHint=False, openWorldHint=False, idempotentHint=False, destructiveHint=False. These are claims by whoever wrote the server, not something we verified.

no output schema sha256 9d964bf5d4347fc5 read 2026-08-27 repository
io.github.pipeworx-io/clash-royale reachable

Clash Royale player, clan, war, tournament, rankings, cards. Supercell dev key.

Send Pipeworx Feedback

Tell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). ONLY for tools served by this Pipeworx connection — if the tool came from a different MCP server in your client (another vendor's Gmail, Splunk, Slack, etc. connector), we cannot fix it and reporting it here only delays you; file it with that server instead. Not sure? Pipeworx tool names are the ones this connection lists. Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt. Filing without an account returns a `claim_token`; pass it back later as pipeworx_feedback({claim_token:"pwfb_…"}) to read whether it was fixed and what changed. The team reads digests daily and signal directly affects roadmap. Rate-limited to 5 per identifier per day. Free; doesn't count against your tool-call quota.

ParameterTypeDescription
type string bug = something broke or returned wrong data. feature = a new tool or capability you wish existed. data_gap = data Pipeworx does not currently expose. praise = positive note. other = anything else.
one of: bug, feature, data_gap, praise, other
context object Optional structured context: which tool, pack, or vertical this relates to.
message string Your feedback in plain text. Be specific (which tool, what error, what data was missing). 1-2 sentences typical, 2000 chars max.
claim_token string Read the reply to a report you filed earlier: pass the `pwfb_…` token that filing returned, with no other arguments. Returns the status and, once resolved, what actually changed.

* required

Author's annotations: readOnlyHint=False, openWorldHint=False, idempotentHint=False, destructiveHint=False. These are claims by whoever wrote the server, not something we verified.

no output schema sha256 9d964bf5d4347fc5 read 2026-08-27 repository
io.github.pipeworx-io/clevelandart reachable

Cleveland Museum of Art Open Access API (~63k artworks, many CC0)

Send Pipeworx Feedback

Tell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). ONLY for tools served by this Pipeworx connection — if the tool came from a different MCP server in your client (another vendor's Gmail, Splunk, Slack, etc. connector), we cannot fix it and reporting it here only delays you; file it with that server instead. Not sure? Pipeworx tool names are the ones this connection lists. Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt. Filing without an account returns a `claim_token`; pass it back later as pipeworx_feedback({claim_token:"pwfb_…"}) to read whether it was fixed and what changed. The team reads digests daily and signal directly affects roadmap. Rate-limited to 5 per identifier per day. Free; doesn't count against your tool-call quota.

ParameterTypeDescription
type string bug = something broke or returned wrong data. feature = a new tool or capability you wish existed. data_gap = data Pipeworx does not currently expose. praise = positive note. other = anything else.
one of: bug, feature, data_gap, praise, other
context object Optional structured context: which tool, pack, or vertical this relates to.
message string Your feedback in plain text. Be specific (which tool, what error, what data was missing). 1-2 sentences typical, 2000 chars max.
claim_token string Read the reply to a report you filed earlier: pass the `pwfb_…` token that filing returned, with no other arguments. Returns the status and, once resolved, what actually changed.

* required

Author's annotations: readOnlyHint=False, openWorldHint=False, idempotentHint=False, destructiveHint=False. These are claims by whoever wrote the server, not something we verified.

no output schema sha256 9d964bf5d4347fc5 read 2026-08-27 repository
io.github.pipeworx-io/clickup reachable

ClickUp MCP — wraps the ClickUp REST API v2 (BYO API key)

Send Pipeworx Feedback

Tell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). ONLY for tools served by this Pipeworx connection — if the tool came from a different MCP server in your client (another vendor's Gmail, Splunk, Slack, etc. connector), we cannot fix it and reporting it here only delays you; file it with that server instead. Not sure? Pipeworx tool names are the ones this connection lists. Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt. Filing without an account returns a `claim_token`; pass it back later as pipeworx_feedback({claim_token:"pwfb_…"}) to read whether it was fixed and what changed. The team reads digests daily and signal directly affects roadmap. Rate-limited to 5 per identifier per day. Free; doesn't count against your tool-call quota.

ParameterTypeDescription
type string bug = something broke or returned wrong data. feature = a new tool or capability you wish existed. data_gap = data Pipeworx does not currently expose. praise = positive note. other = anything else.
one of: bug, feature, data_gap, praise, other
context object Optional structured context: which tool, pack, or vertical this relates to.
message string Your feedback in plain text. Be specific (which tool, what error, what data was missing). 1-2 sentences typical, 2000 chars max.
claim_token string Read the reply to a report you filed earlier: pass the `pwfb_…` token that filing returned, with no other arguments. Returns the status and, once resolved, what actually changed.

* required

Author's annotations: readOnlyHint=False, openWorldHint=False, idempotentHint=False, destructiveHint=False. These are claims by whoever wrote the server, not something we verified.

no output schema sha256 9d964bf5d4347fc5 read 2026-08-27 repository
io.github.pipeworx-io/climate reachable

Climate MCP — wraps Open-Meteo Climate API (free, no auth)

Send Pipeworx Feedback

Tell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). ONLY for tools served by this Pipeworx connection — if the tool came from a different MCP server in your client (another vendor's Gmail, Splunk, Slack, etc. connector), we cannot fix it and reporting it here only delays you; file it with that server instead. Not sure? Pipeworx tool names are the ones this connection lists. Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt. Filing without an account returns a `claim_token`; pass it back later as pipeworx_feedback({claim_token:"pwfb_…"}) to read whether it was fixed and what changed. The team reads digests daily and signal directly affects roadmap. Rate-limited to 5 per identifier per day. Free; doesn't count against your tool-call quota.

ParameterTypeDescription
type string bug = something broke or returned wrong data. feature = a new tool or capability you wish existed. data_gap = data Pipeworx does not currently expose. praise = positive note. other = anything else.
one of: bug, feature, data_gap, praise, other
context object Optional structured context: which tool, pack, or vertical this relates to.
message string Your feedback in plain text. Be specific (which tool, what error, what data was missing). 1-2 sentences typical, 2000 chars max.
claim_token string Read the reply to a report you filed earlier: pass the `pwfb_…` token that filing returned, with no other arguments. Returns the status and, once resolved, what actually changed.

* required

Author's annotations: readOnlyHint=False, openWorldHint=False, idempotentHint=False, destructiveHint=False. These are claims by whoever wrote the server, not something we verified.

no output schema sha256 9d964bf5d4347fc5 read 2026-08-27 repository
io.github.pipeworx-io/climate-feeds reachable

Climate & Energy Feeds MCP.

Send Pipeworx Feedback

Tell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). ONLY for tools served by this Pipeworx connection — if the tool came from a different MCP server in your client (another vendor's Gmail, Splunk, Slack, etc. connector), we cannot fix it and reporting it here only delays you; file it with that server instead. Not sure? Pipeworx tool names are the ones this connection lists. Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt. Filing without an account returns a `claim_token`; pass it back later as pipeworx_feedback({claim_token:"pwfb_…"}) to read whether it was fixed and what changed. The team reads digests daily and signal directly affects roadmap. Rate-limited to 5 per identifier per day. Free; doesn't count against your tool-call quota.

ParameterTypeDescription
type string bug = something broke or returned wrong data. feature = a new tool or capability you wish existed. data_gap = data Pipeworx does not currently expose. praise = positive note. other = anything else.
one of: bug, feature, data_gap, praise, other
context object Optional structured context: which tool, pack, or vertical this relates to.
message string Your feedback in plain text. Be specific (which tool, what error, what data was missing). 1-2 sentences typical, 2000 chars max.
claim_token string Read the reply to a report you filed earlier: pass the `pwfb_…` token that filing returned, with no other arguments. Returns the status and, once resolved, what actually changed.

* required

Author's annotations: readOnlyHint=False, openWorldHint=False, idempotentHint=False, destructiveHint=False. These are claims by whoever wrote the server, not something we verified.

no output schema sha256 9d964bf5d4347fc5 read 2026-08-27 repository
io.github.pipeworx-io/climatiq reachable

Climatiq MCP — carbon footprint calculator with emission factors

Send Pipeworx Feedback

Tell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). ONLY for tools served by this Pipeworx connection — if the tool came from a different MCP server in your client (another vendor's Gmail, Splunk, Slack, etc. connector), we cannot fix it and reporting it here only delays you; file it with that server instead. Not sure? Pipeworx tool names are the ones this connection lists. Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt. Filing without an account returns a `claim_token`; pass it back later as pipeworx_feedback({claim_token:"pwfb_…"}) to read whether it was fixed and what changed. The team reads digests daily and signal directly affects roadmap. Rate-limited to 5 per identifier per day. Free; doesn't count against your tool-call quota.

ParameterTypeDescription
type string bug = something broke or returned wrong data. feature = a new tool or capability you wish existed. data_gap = data Pipeworx does not currently expose. praise = positive note. other = anything else.
one of: bug, feature, data_gap, praise, other
context object Optional structured context: which tool, pack, or vertical this relates to.
message string Your feedback in plain text. Be specific (which tool, what error, what data was missing). 1-2 sentences typical, 2000 chars max.
claim_token string Read the reply to a report you filed earlier: pass the `pwfb_…` token that filing returned, with no other arguments. Returns the status and, once resolved, what actually changed.

* required

Author's annotations: readOnlyHint=False, openWorldHint=False, idempotentHint=False, destructiveHint=False. These are claims by whoever wrote the server, not something we verified.

no output schema sha256 9d964bf5d4347fc5 read 2026-08-27 repository
io.github.pipeworx-io/clinicaltables reachable

NIH Clinical Tables: ICD-10/9, RxTerms, LOINC, NPI, conditions search. Keyless.

Send Pipeworx Feedback

Tell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). ONLY for tools served by this Pipeworx connection — if the tool came from a different MCP server in your client (another vendor's Gmail, Splunk, Slack, etc. connector), we cannot fix it and reporting it here only delays you; file it with that server instead. Not sure? Pipeworx tool names are the ones this connection lists. Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt. Filing without an account returns a `claim_token`; pass it back later as pipeworx_feedback({claim_token:"pwfb_…"}) to read whether it was fixed and what changed. The team reads digests daily and signal directly affects roadmap. Rate-limited to 5 per identifier per day. Free; doesn't count against your tool-call quota.

ParameterTypeDescription
type string bug = something broke or returned wrong data. feature = a new tool or capability you wish existed. data_gap = data Pipeworx does not currently expose. praise = positive note. other = anything else.
one of: bug, feature, data_gap, praise, other
context object Optional structured context: which tool, pack, or vertical this relates to.
message string Your feedback in plain text. Be specific (which tool, what error, what data was missing). 1-2 sentences typical, 2000 chars max.
claim_token string Read the reply to a report you filed earlier: pass the `pwfb_…` token that filing returned, with no other arguments. Returns the status and, once resolved, what actually changed.

* required

Author's annotations: readOnlyHint=False, openWorldHint=False, idempotentHint=False, destructiveHint=False. These are claims by whoever wrote the server, not something we verified.

no output schema sha256 9d964bf5d4347fc5 read 2026-08-27 repository
io.github.pipeworx-io/clinicaltrials reachable

ClinicalTrials MCP — wraps ClinicalTrials.gov API v2 (free, no auth)

Send Pipeworx Feedback

Tell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). ONLY for tools served by this Pipeworx connection — if the tool came from a different MCP server in your client (another vendor's Gmail, Splunk, Slack, etc. connector), we cannot fix it and reporting it here only delays you; file it with that server instead. Not sure? Pipeworx tool names are the ones this connection lists. Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt. Filing without an account returns a `claim_token`; pass it back later as pipeworx_feedback({claim_token:"pwfb_…"}) to read whether it was fixed and what changed. The team reads digests daily and signal directly affects roadmap. Rate-limited to 5 per identifier per day. Free; doesn't count against your tool-call quota.

ParameterTypeDescription
type string bug = something broke or returned wrong data. feature = a new tool or capability you wish existed. data_gap = data Pipeworx does not currently expose. praise = positive note. other = anything else.
one of: bug, feature, data_gap, praise, other
context object Optional structured context: which tool, pack, or vertical this relates to.
message string Your feedback in plain text. Be specific (which tool, what error, what data was missing). 1-2 sentences typical, 2000 chars max.
claim_token string Read the reply to a report you filed earlier: pass the `pwfb_…` token that filing returned, with no other arguments. Returns the status and, once resolved, what actually changed.

* required

Author's annotations: readOnlyHint=False, openWorldHint=False, idempotentHint=False, destructiveHint=False. These are claims by whoever wrote the server, not something we verified.

no output schema sha256 9d964bf5d4347fc5 read 2026-08-27 repository
io.github.pipeworx-io/close-crm reachable

Close CRM MCP Pack — wraps the Close (close.com) API v1.

Send Pipeworx Feedback

Tell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). ONLY for tools served by this Pipeworx connection — if the tool came from a different MCP server in your client (another vendor's Gmail, Splunk, Slack, etc. connector), we cannot fix it and reporting it here only delays you; file it with that server instead. Not sure? Pipeworx tool names are the ones this connection lists. Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt. Filing without an account returns a `claim_token`; pass it back later as pipeworx_feedback({claim_token:"pwfb_…"}) to read whether it was fixed and what changed. The team reads digests daily and signal directly affects roadmap. Rate-limited to 5 per identifier per day. Free; doesn't count against your tool-call quota.

ParameterTypeDescription
type string bug = something broke or returned wrong data. feature = a new tool or capability you wish existed. data_gap = data Pipeworx does not currently expose. praise = positive note. other = anything else.
one of: bug, feature, data_gap, praise, other
context object Optional structured context: which tool, pack, or vertical this relates to.
message string Your feedback in plain text. Be specific (which tool, what error, what data was missing). 1-2 sentences typical, 2000 chars max.
claim_token string Read the reply to a report you filed earlier: pass the `pwfb_…` token that filing returned, with no other arguments. Returns the status and, once resolved, what actually changed.

* required

Author's annotations: readOnlyHint=False, openWorldHint=False, idempotentHint=False, destructiveHint=False. These are claims by whoever wrote the server, not something we verified.

no output schema sha256 9d964bf5d4347fc5 read 2026-08-27 repository
io.github.pipeworx-io/cloudflare-radar reachable

Cloudflare Radar MCP — internet observatory (traffic, attacks, BGP, quality)

Send Pipeworx Feedback

Tell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). ONLY for tools served by this Pipeworx connection — if the tool came from a different MCP server in your client (another vendor's Gmail, Splunk, Slack, etc. connector), we cannot fix it and reporting it here only delays you; file it with that server instead. Not sure? Pipeworx tool names are the ones this connection lists. Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt. Filing without an account returns a `claim_token`; pass it back later as pipeworx_feedback({claim_token:"pwfb_…"}) to read whether it was fixed and what changed. The team reads digests daily and signal directly affects roadmap. Rate-limited to 5 per identifier per day. Free; doesn't count against your tool-call quota.

ParameterTypeDescription
type string bug = something broke or returned wrong data. feature = a new tool or capability you wish existed. data_gap = data Pipeworx does not currently expose. praise = positive note. other = anything else.
one of: bug, feature, data_gap, praise, other
context object Optional structured context: which tool, pack, or vertical this relates to.
message string Your feedback in plain text. Be specific (which tool, what error, what data was missing). 1-2 sentences typical, 2000 chars max.
claim_token string Read the reply to a report you filed earlier: pass the `pwfb_…` token that filing returned, with no other arguments. Returns the status and, once resolved, what actually changed.

* required

Author's annotations: readOnlyHint=False, openWorldHint=False, idempotentHint=False, destructiveHint=False. These are claims by whoever wrote the server, not something we verified.

no output schema sha256 9d964bf5d4347fc5 read 2026-08-27 repository
io.github.pipeworx-io/cms-open-payments reachable

CMS Open Payments, with annual dataset discovery through the official DKAN API.

Send Pipeworx Feedback

Tell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). ONLY for tools served by this Pipeworx connection — if the tool came from a different MCP server in your client (another vendor's Gmail, Splunk, Slack, etc. connector), we cannot fix it and reporting it here only delays you; file it with that server instead. Not sure? Pipeworx tool names are the ones this connection lists. Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt. Filing without an account returns a `claim_token`; pass it back later as pipeworx_feedback({claim_token:"pwfb_…"}) to read whether it was fixed and what changed. The team reads digests daily and signal directly affects roadmap. Rate-limited to 5 per identifier per day. Free; doesn't count against your tool-call quota.

ParameterTypeDescription
type string bug = something broke or returned wrong data. feature = a new tool or capability you wish existed. data_gap = data Pipeworx does not currently expose. praise = positive note. other = anything else.
one of: bug, feature, data_gap, praise, other
context object Optional structured context: which tool, pack, or vertical this relates to.
message string Your feedback in plain text. Be specific (which tool, what error, what data was missing). 1-2 sentences typical, 2000 chars max.
claim_token string Read the reply to a report you filed earlier: pass the `pwfb_…` token that filing returned, with no other arguments. Returns the status and, once resolved, what actually changed.

* required

Author's annotations: readOnlyHint=False, openWorldHint=False, idempotentHint=False, destructiveHint=False. These are claims by whoever wrote the server, not something we verified.

no output schema sha256 9d964bf5d4347fc5 read 2026-08-27 repository
← previous more servers →

What this page is

Every field above is reproduced as the server published it at the time shown. The description and the annotations are claims by the server's author. Toolpin does not call tools, so we cannot tell you whether a tool does what it says.

What we can tell you is whether the claim changed. The hash covers the fields the MCP specification defines, so a vendor build stamp does not move it but a rewritten description does. See how we monitor, or this server's change history.