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/tatoeba reachable

Tatoeba multilingual sentence corpus (~13M sentences, 400+ languages)

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/tavily reachable

Tavily MCP — wraps the Tavily API (tavily.com)

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/tax-regulations reachable

Tax Regulations MCP — US Treasury / IRS regulations (26 CFR, 'Treas. Reg.').

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/tcgdex reachable

TCGdex MCP — multi-language open trading card game database (Pokémon TCG and more).

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/tech-feeds reachable

Tech 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/temperature-random reachable

temperature-random MCP — wraps StupidAPIs (requires X-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/tenor reachable

Tenor GIFs/stickers v2: search, featured, categories, trending, posts.

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/textcase reachable

Text case conversion 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/textstats reachable

Text statistics & readability 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/tfl reachable

Transport for London (TfL) Unified API 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/theaudiodb reachable

TheAudioDB MCP — community music metadata database.

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/the-committee reachable

the-committee MCP — wraps StupidAPIs (requires X-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/thegamesdb reachable

TheGamesDB MCP — wraps TheGamesDB API (thegamesdb.net), a community

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/the-graph reachable

The Graph MCP — indexed blockchain data via subgraph GraphQL queries

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/the-guardian reachable

Guardian Open Platform: content search, articles, sections, tags. Free 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/themeparks reachable

ThemeParks.wiki MCP — live theme park wait times, schedules, and attraction data.

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/thesportsdb reachable

TheSportsDB MCP — sports catalog (teams, players, events)

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/threatfox reachable

ThreatFox MCP — abuse.ch indicator-of-compromise feed (free, key 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/ticketmaster reachable

Ticketmaster Discovery v2 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/tides error

Tides MCP — NOAA Tides and Currents data

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-26 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.