S
AI App
Connected
SpecterSystems.io
by Specter Systems (Community)
Available in: US FR GB ES KR IN
Available on:
ChatGPT
Description
Specter Systems helps merchants and brokers complete business financing intake, upload bank statements and supporting documents, and track financing applications. Authenticated Specter users can review their own recent applications, facilities, lender submissions, and offer status.
Capabilities
No special capabilities listed
AI Agent Discovery
SpecterSystems.io is indexed by Tedix as a structured ai application listing for AI assistants, search crawlers, and users comparing agent-ready apps.
- SpecterSystems.io is categorized as AI application.
- Developer: Specter Systems.
- Connector type: AI-Powered App.
- Current connector status: Connected.
- Observed distribution channels: chatgpt.
- Available regions: US, FR, GB, ES, KR, IN.
Use this page to understand whether SpecterSystems.io is relevant for ai application workflows in AI assistants.
For MCP discovery, this listing helps crawlers connect SpecterSystems.io to tool, resource, prompt, and server-health signals instead of treating it as a generic directory entry.
The canonical Tedix directory URL is https://tedix.dev/apps/spectersystemsio/.
Crawlable Profile
Source and availability
Tedix identifies SpecterSystems.io from Upstream Mcp tool source; Store sources: ChatGPT app store; Distribution: Ecosystem Directory. Availability is reported for US, FR, GB, ES, KR, IN.
- ChatGPT app store Auth required · RELEASED · US, FR, GB, ES, KR, IN
Auth, tools, and actions
Authentication: Requires Login. No special capability flags are currently listed. Current MCP inventory reports 56 tools, 6 resources, and 0 prompts.
- Compare Application Offers · Read-only action
Reads and compares available offers for one authenticated facility/application. Use when the user asks which offer is better or wants financing terms side by side. This is read-only.
- Create Application Facility · External-world action
Creates an authenticated facility/application record inside the user's Specter tenant. Use for internal users or brokers who explicitly ask to create a facility after authentication. This is additive but writes live CRM/FOS data.
- Create Lender Submission · External-world action
Creates an authenticated lender submission for a specific facility/application. Use only when the user explicitly asks to submit or prepare a facility for a lender. This writes live submission pipeline data.
- Create Workflow Draft · External-world action
Creates a new inactive Workflow V3 draft for the authenticated tenant. Use only after the user asks to create a workflow and the graph has been validated or intentionally saved as an incomplete draft. The MCP server forces is_draft=true and is_active=false; publish_workflow is required to activate live automation.
- Get Application Details · Read-only action
Gets one authenticated facility/application by ID, including currently available related entities and pipeline status. For entity-specific questions about one known facility/application, call this first with the known facility_id instead of doing a broad search. Use before submission-list tools when the user asks for that facility's status, approval posture, offers, lender outcomes, or history. Requires account authorization and does not mutate data.
- Get Application History · Read-only action
Reads timeline/history for a facility/application visible to the authenticated user, including related activity/events the backend exposes. Use when the user asks what happened on an application or wants recent changes. It is read-only.
- Get Bank Statement · Read-only action
Gets one bank statement visible to the authenticated user. Use when the user asks for statement details, analysis, linked facility, risk signals, or included periods. It is read-only.
- Get Bank Statement History · Read-only action
Reads timeline/history for a bank statement visible to the authenticated user. Use when the user asks how a statement or its analysis changed. It is read-only.
Plus 48 additional actions in the full tool inventory.
Verification freshness
- Catalog synced 14h ago (June 6, 2026)
- Connector checked 11h ago (June 6, 2026)
- MCP scanned 11h ago (June 6, 2026)
- Directory updated 11h ago (June 6, 2026)
Publisher Intelligence
Insights and recommendations for app publishers. See how your app performs and how to improve discoverability.
Server Status specter-fos-mcp v0.3.0
Tools
Resources
Prompts
https://mcp.spectersystems.io/mcp Last checked: 11h ago
Technical Details
Connection Latency 875ms
Tools(56)
Showing 56 of 56 tools
Sorted by toolName
| Tool | Description | Flags | Test | Last Tested | |
|---|---|---|---|---|---|
compare_application_offers | Reads and compares available offers for one authenticated facility/application. Use when the user asks which offer is better or wants financing terms side by side. This is read-only. | read-only | 0%Latency 556ms | 10h ago | |
create_application_facility | Creates an authenticated facility/application record inside the user's Specter tenant. Use for internal users or brokers who explicitly ask to create a facility after authentication. This is additive but writes live CRM/FOS data. | — | 0%Latency 457ms | 10h ago | |
create_lender_submission | Creates an authenticated lender submission for a specific facility/application. Use only when the user explicitly asks to submit or prepare a facility for a lender. This writes live submission pipeline data. | — | 0%Latency 519ms | 10h ago | |
create_workflow_draft | Creates a new inactive Workflow V3 draft for the authenticated tenant. Use only after the user asks to create a workflow and the graph has been validated or intentionally saved as an incomplete draft. The MCP server forces is_draft=true and is_active=false; publish_workflow is required to activate live automation. | — | 0%Latency 458ms | 10h ago | |
get_application_details | Gets one authenticated facility/application by ID, including currently available related entities and pipeline status. For entity-specific questions about one known facility/application, call this first with the known facility_id instead of doing a broad search. Use before submission-list tools when the user asks for that facility's status, approval posture, offers, lender outcomes, or history. Requires account authorization and does not mutate data. | read-only | 0%Latency 471ms | 10h ago | |
get_application_history | Reads timeline/history for a facility/application visible to the authenticated user, including related activity/events the backend exposes. Use when the user asks what happened on an application or wants recent changes. It is read-only. | read-only | 0%Latency 464ms | 10h ago | |
get_bank_statement | Gets one bank statement visible to the authenticated user. Use when the user asks for statement details, analysis, linked facility, risk signals, or included periods. It is read-only. | read-only | 0%Latency 457ms | 10h ago | |
get_bank_statement_history | Reads timeline/history for a bank statement visible to the authenticated user. Use when the user asks how a statement or its analysis changed. It is read-only. | read-only | 0%Latency 449ms | 10h ago | |
get_bank_statement_period | Gets one bank statement period visible to the authenticated user. Use for period-level revenue, balances, NSF, DSR, fraud, and MCA-position analysis. It is read-only. | read-only | 0%Latency 461ms | 10h ago | |
get_communication_channel_for_entity | Gets the communication channel for a specific entity visible to the authenticated user. Use before reading or sending messages tied to a facility, submission, lead, counterparty, or lender. It is read-only. | read-only | 0%Latency 461ms | 10h ago | |
get_lender_submission | Gets one lender submission visible to the authenticated user. Use when the user asks for lender submission details, current status, requested terms, offered terms, approved terms, or lender response context. It is read-only and tenant/user scope is enforced by the backend. | read-only | 0%Latency 453ms | 10h ago | |
get_my_specter_profile | Reads the authenticated user's Specter profile, active tenant, and role context. Use before user-specific application, facility, or submission requests to confirm identity and authorization. Requires a connected Specter account or bearer token; it does not mutate data. | read-only | 0%Latency 445ms | 10h ago | |
get_public_application_form | Fetches the public signed intake form for a merchant or broker without requiring a Specter user account. Use when a non-user wants to apply for business financing or a broker wants to start signup. It returns the live form schema and public bank-login/upload configuration; it does not submit anything. | read-only | 100%Latency 657ms | 10h ago | |
get_submission_history | Reads timeline/history for a lender submission visible to the authenticated user. Use when the user asks for submission history, status changes, lender events, or related activity. It is read-only. | read-only | 0%Latency 467ms | 10h ago | |
get_tax_return | Gets one tax return visible to the authenticated user. Use when the user asks for tax return details, years, profitability summary, linked application, or risk signals. It is read-only. | read-only | 0%Latency 453ms | 10h ago | |
get_tax_return_history | Reads timeline/history for a tax return visible to the authenticated user. Use when the user asks how a tax return or its analysis changed. It is read-only. | read-only | 0%Latency 451ms | 10h ago | |
get_tax_return_year | Gets one tax return year visible to the authenticated user. Use for annual tax metrics, extracted fields, profitability, ownership, and document URLs. It is read-only. | read-only | 0%Latency 457ms | 10h ago | |
get_workflow_fos_entity_fields | Reads the field schema for one FOS entity type available to Workflow V3. Use before configuring conditions, mappings, or node data fields. It is read-only. | read-only | 0%Latency 444ms | 10h ago | |
list_application_bank_statements | Lists bank statement records visible to the authenticated user, optionally filtered to one facility/application, counterparty, or status. Use when the user asks for statements, statement files, processing state, or statement analysis linked to an application. It is read-only. | read-only | Not tested | — | |
list_application_submissions | Lists lender submissions visible to the authenticated user, optionally filtered to one facility/application, lender, status, or recent-day window. For a specific facility/application, pass only query.facility_id unless the user explicitly named a specific lender/status/time window; never send placeholder values such as 0, empty strings, or unknown capital_source_id. Use after get_application_details for entity-specific submission status, approvals, declines, offers, and lender history. It is read-only. | read-only | Not tested | — | |
list_application_tax_returns | Lists tax return records visible to the authenticated user, optionally filtered to one facility/application, counterparty, or status. Use when the user asks for tax returns, profitability, tax years, or tax-document analysis linked to an application. It is read-only. | read-only | Not tested | — | |
list_available_email_senders | Lists email sender identities available to the authenticated user. Use before sending email through MCP so the user can pick a permitted sender. It is read-only. | read-only | Not tested | — | |
list_bank_statement_periods | Lists periods/months for a bank statement visible to the authenticated user. Use when the user asks for monthly revenue, balances, NSF counts, DSR, fraud signals, or period-level statement details. It is read-only. | read-only | Not tested | — | |
list_channel_messages | Lists messages in a communication channel visible to the authenticated user. Use to retrieve SMS, email, internal notes, or thread context before answering or sending. It is read-only. | read-only | Not tested | — | |
list_communication_channels | Lists communication channels visible to the authenticated user. Use when the user wants recent SMS/email/internal conversation context for applications, submissions, leads, or counterparties. It is read-only. | read-only | Not tested | — | |
list_conversation_messages | Lists messages in a conversation visible to the authenticated user. Use when a user asks for a specific SMS/email conversation thread. It is read-only. | read-only | Not tested | — | |
list_email_records | Lists email audit records visible to the authenticated user, optionally filtered by facility, submission, lead, counterparty, direction, sender, or recipient. Use when the user asks for recent email activity or lender email history. It is read-only. | read-only | Not tested | — | |
list_my_recent_applications | Lists recent financing application/facility records visible to the authenticated user. Use when the user asks what applications, deals, facilities, or funding requests they recently have in Specter. Filters are intentionally narrow: page size, recent-day window, status/stage, and search text. | read-only | Not tested | — | |
list_sms_records | Lists SMS audit records visible to the authenticated user, optionally filtered by facility, submission, lead, counterparty, direction, or phone. Use when the user asks for recent SMS activity or text-message history. It is read-only. | read-only | Not tested | — | |
list_tax_return_years | Lists year-level records for a tax return visible to the authenticated user. Use when the user asks for annual tax metrics, revenue, profitability, ownership, or extracted year details. It is read-only. | read-only | Not tested | — | |
list_workflow_builder_catalog | Reads the authenticated tenant's Workflow V3 builder catalog, including available triggers, node categories, FOS actions, handles, and field configuration needed to design a Temporal-backed workflow. Use this before creating or changing workflows so the assistant only uses supported node vocabulary. It is read-only. | read-only | Not tested | — | |
list_workflow_fos_entities | Lists FOS entity types available to Workflow V3 configuration for the authenticated tenant. Use before building entity-triggered workflows or field conditions. It is read-only. | read-only | Not tested | — | |
list_workflow_node_types | Reads the registered Workflow V3 node types and categories available to the authenticated tenant. Use when selecting or explaining valid workflow nodes. It is read-only and must be used instead of inventing node type names. | read-only | Not tested | — | |
publish_workflow | Publishes a validated Workflow V3 draft for the authenticated tenant. Use only after validation passes, the assistant summarizes the affected trigger/actions, and the user explicitly confirms publishing. This can activate live Temporal automation, so the input requires confirm_publish=true. | destructive | Not tested | — | |
recalculate_bank_statement | Recalculates stored bank statement aggregates and risk signals for one visible statement. Use only when the user asks to refresh/recalculate statement analysis. This writes derived analysis fields and may affect underwriting views. | destructive | Not tested | — | |
recalculate_tax_return | Recalculates stored tax return risk/profile analysis for one visible tax return. Use only when the user asks to refresh/recalculate tax-return analysis. This writes derived analysis fields and may affect underwriting views. | destructive | Not tested | — | |
refresh_specter_session | Refreshes an existing Specter Systems session with a refresh token from the auth backend. Use only when app-level OAuth is unavailable and an authenticated user's access token has expired. It sends the refresh token in the Authorization header; model-visible output redacts new tokens and secrets. | — | Not tested | — | |
search_workflow_agents | Searches/list agents in the authenticated tenant for Workflow V3 assignment configuration. Use to resolve a named user/agent or current profile user to a verified agent_id before configuring assignment actions or task assignee_id. It is read-only; never invent an agent_id if no exact or clearly intended match is returned. | read-only | Not tested | — | |
search_workflow_builder_tools | Locally analyzes a user's Workflow V3 request and returns the likely FOS entity, trigger, fields, operators, action node types, and minimal next MCP calls. Use this as the first Workflow Builder tool call before loading broad catalogs, so the assistant can retrieve only the small schemas needed for the requested workflow. This tool does not call external systems or access tenant records. | read-only | Not tested | — | |
select_specter_tenant | Completes sign-in for users who have access to more than one tenant. Use after sign_in_to_specter returns requires_tenant_selection=true. It sends the tenant_selection_token and selected tenant_id to the live auth backend; model-visible output redacts session tokens and secrets. | — | Not tested | — | |
send_channel_message | Sends a message in a visible communication channel as the authenticated user. Use only after the user explicitly asks to send or reply. For email/SMS, include only the intended recipient fields and message body; backend sender permissions, channel access, dispatch, and audit logging apply. | destructive | Not tested | — | |
send_conversation_message | Sends a reply in a visible conversation as the authenticated user. Use only after the user explicitly asks to send or reply. The backend fills the conversation recipient, verifies sender access, dispatches email/SMS where applicable, and records audit data. | destructive | Not tested | — | |
show_application_summary | Renders a compact application or intake summary card from already retrieved data. Use after a data tool when a concise visual summary helps the user. This render-only tool does not call external systems or mutate data. | read-only | Not tested | — | |
sign_in_to_specter | Authenticates an existing Specter Systems user with email and password. Use only when the user explicitly asks to sign in and app-level OAuth is unavailable. This calls the live auth backend and may return a tenant-selection challenge; model-visible output redacts session tokens and secrets. It does not create, update, or delete CRM/FOS business records. | — | Not tested | — | |
submit_public_financing_application | Submits a completed public financing application for a merchant or broker. Use only after the applicant reviews the answers and consents to submit them to Specter Systems. This creates or updates live intake/application records and may trigger downstream intake automation. Do not collect or submit SSNs, payment card data, health data, or unrelated personal data. | — | Not tested | — | |
transition_application_stage | Transitions an authenticated facility/application to a lifecycle stage accepted by the FOS workflow. Use only when the user explicitly asks to move an application stage. Backend lifecycle gates, tenant isolation, permission checks, notifications, and audit history apply. | destructive | Not tested | — | |
update_bank_statement | Updates narrow bank statement header fields visible to the authenticated user. Use only when the user explicitly asks to correct statement metadata such as status, folder URL, or notes. Do not use to submit raw financial account credentials or card data. | destructive | Not tested | — | |
update_bank_statement_period | Updates narrow period-level bank statement analysis fields visible to the authenticated user. Use only when the user explicitly asks to correct extracted period metrics. Do not collect full account credentials, card data, or unrelated sensitive data. | destructive | Not tested | — | |
update_lender_submission | Updates narrow fields on a lender submission visible to the authenticated user, such as notes, lender response, contact, requested terms, offered terms, and approved terms. Use only after the user asks to change those submission details. Backend permissions, tenant isolation, validation, and audit/event handling still apply. | destructive | Not tested | — | |
update_lender_submission_status | Transitions an authenticated lender submission to a new workflow status. Use only when the user explicitly asks to update status. This may trigger notifications or downstream workflow behavior, so it is marked destructive. | destructive | Not tested | — | |
update_tax_return | Updates narrow tax return header fields visible to the authenticated user, such as name, status, folder URL, and profitability summary. Use only when the user explicitly asks to correct tax return metadata. | destructive | Not tested | — | |
update_tax_return_year | Updates narrow year-level tax return analysis fields visible to the authenticated user. Use only when the user explicitly asks to correct extracted tax-year metrics. Do not collect or submit SSNs through this tool. | destructive | Not tested | — | |
update_workflow_draft | Updates an existing Workflow V3 definition for the authenticated tenant. Use when the user approves changes to a draft or wants to repair validation errors. Validate the updated graph before publish. Backend tenant permissions and validation still apply. | — | Not tested | — | |
upload_public_bank_statement | Uploads a bank statement or supporting document to a specific public signed-form submission field. Use only when the applicant has supplied a file for their application. This writes the file to live Specter storage and can replace the file association for that form field depending on backend rules. | destructive | Not tested | — | |
validate_public_financing_application | Validates a public merchant or broker application before final submission. Use after collecting answers from the signed form. The applicant_data object must contain only fields from the fetched form schema; do not request SSNs, card data, health data, or unrelated personal data. | read-only | Not tested | — | |
validate_workflow_draft | Validates a proposed Workflow V3 graph without saving or publishing it. Use after drafting or modifying a workflow and before create, update, publish, or execution. Inputs must use registered triggers, node types, handles, and config schemas from the workflow catalog. | read-only | Not tested | — |
Discoverability Score
54
Fair
54 of 100 — how easily AI agents find your app
- Description quality20/20
- Example prompts0/20
- Keyword coverage0/15
- Tool metadata20/20
- Visual assets0/20
- Endpoint health10/10
- Data freshness15/15
How to Improve
Add at least 2 example prompts. Prompt examples strongly improve app matching and click-through intent.
Increase keyword coverage (discovery + trigger) to improve retrieval for long-tail queries.
Provide a stable HTTPS logo URL (avoid connectors://) so cards render consistently across clients.
Add at least 2 screenshots that show real workflows to increase confidence and conversion.
Technical Details
- Status
- ENABLED
- Type
- AI-Powered App
- Auth
- Requires Login
- Listed on
- ChatGPT
- Added
- June 5, 2026
- Last synced
- 14h ago
- Last checked
- 11h ago
- Version
- 0.3.0
- Distribution
- Ecosystem Directory