Vendor: usemotion.com · entry id 10-motion · source 10-scheduling-routing.md line 122
A working server exists but somebody other than the vendor built it. It can be abandoned without the vendor noticing. The status was established on 2026-08-24 and has not been re-fetched since.
mcp_status, verbatim from the file:
community
mcp_url, verbatim from the file:
https://github.com/RF-D/motion-mcp (one of several competing unofficial servers; also github.com/devondragon/MotionMCP, github.com/h3ro-dev/motion-mcp-server, github.com/christopher-czaban/motion-mcp-server, github.com/Identityex/use-motion-mcp-server) - the RF-D repo states plainly: "This is a community-built integration, not an official Motion product."
api_gate, verbatim from the file:
paid - Motion has no free tier at all (Pro AI $19/seat/mo, Business AI $29/seat/mo are the only listed plans); API access requires an API key issued to a paid account.
No documentation URL recorded.
263 of 293 entries are in the same position. Blank is legal and it is published as blank.
Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build.
The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale.
A github.com URL already appears somewhere in this entry, which is a seed for that rail and not a measurement of repo health:
A job tag means the vendor says the tool does this. It is not a test result, not proof the capability is reachable through the tool's MCP server, and not proof it is available on the gate this entry records.
Tagged by machine-pass on 2026-08-25 against the closed 55 job vocabulary. 271 of 293 entries carry at least one tag; 827 tags are assigned in total.
7 source URLs. Raw sources field, verbatim:
https://usemotion.com, https://www.usemotion.com/pricing, https://www.usemotion.com/help, https://api-docs.usemotion.com/, https://docs.usemotion.com/, https://github.com/RF-D/motion-mcp, https://mcp.so/servers/motion-mcp-server
Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the methodology page.