Fieldproxy vs tech.techpool/techpool
Fieldproxy is an MCP server published by Fieldproxy. Marketplaces we read that list it: 1 (Official MCP Registry). tech.techpool/techpool is an MCP server published by techpool.tech. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Fieldproxy | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.0.0 No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Fieldproxy | tech.techpool/techpool |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (api-us-east-1.fieldproxy.ai/mcp) | Remote server (mcp.techpool.tech/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/fieldproxy/fieldproxy-mcp | Not stated |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-13 |
| Endpoint at the last check | not checked yet | not checked yet |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Fieldproxy
Field service management: jobs, dispatch, invoices, quotes and building apps, confirm before change.
tech.techpool/techpool
Field service management: missions, schedule, field work reports, clients and timesheets.
How to run each
Fieldproxy As a remote MCP server
claude mcp add --transport http fieldproxy-mcp https://api-us-east-1.fieldproxy.ai/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
tech.techpool/techpool As a remote MCP server
claude mcp add --transport http techpool https://mcp.techpool.tech/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Fieldproxy · What it can do: tech.techpool/techpool · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.