What to check when the 1099Policy MCP server does not behave as expected. For setup and security, see MCP server; for every tool's inputs and returns, see the tool reference.
Connecting
The browser never opens after adding the server. The client has to support remote MCP servers with OAuth; check that the URL is exactly https://mcp.1099policy.com/mcp and that the entry is a remote/HTTP server, not a command.
The approval page says "No organization is selected". Open the dashboard, choose an organization in the switcher, then follow the connection link again.
The approval page shows a red warning about an unverified client. The client's redirect is not one 1099Policy recognises. If you started the connection from that application yourself, Allow anyway is safe; if a link brought you here, close the tab.
ChatGPT does not show the option to create a connector. Custom connectors require a plan that includes them and, on some plans, developer mode turned on in settings.
Requests fail with an authorization error. The connection was disconnected, or the key was revoked or belongs to a different environment than expected. Connect again.
A direct curl returns an error before reaching a tool. The Accept header must list both application/json and text/event-stream.
Permissions and organizations
The assistant says a write tool is not available. The connection was approved read-only. Disconnect it under Developers → Connected assistants and connect again choosing Make changes.
The assistant cannot switch organizations at all. Connections made with an API key are bound to that key's organization and have no switcher; use a browser-approved connection, or a separate key per organization.
Answers that look wrong
A bind came back with bound: false. Read the note. Either the contractor is already covered, or they hold no policy of ours to attach — send them an application link instead.
A contractor with their own insurance shows in the coverage-gap list. The gap sweep counts 1099Policy policies. Ask about that contractor directly; the assistant reads their uploaded certificate and reports the review.
A quote for an hourly job looks too low. For an hourly job the wage is one hour's pay, so premiumOwed prices that hour plus the fixed fees, not the whole job. The premium actually billed follows the hours reported each pay period.
A quote came back without a premium. premiumOwed is null when the premium cannot be worked out yet; the premiumNote says why. The assistant says so rather than estimating.
A count seems low. Check whether the tool returned complete: false. If so the assistant held one page of results and should fetch more before stating a count or an absence.
A submitted certificate has no review result yet. Review runs asynchronously. Poll with getCertificate until settled is true.
Questions
Email integration@1099policy.com. Privacy policy: 1099policy.com/legal/privacy.