Skip to main content
Glama
Sign In
Orion Vision MCP Server

Orion Vision MCP Server

by Cognitive-Stack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Orion Vision MCP Server

No user-submitted related servers found.

    Related Servers

    • Loupe MCP

      Loupe MCPofficial

      coreprocess
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to turn PDFs, scans, photos, Office files, and HTML into readable text through signed-URL uploads and batch jobs, using fast page-level OCR or accurate vision-reconciled transcription. Jobs run independently, support page-by-page reading and downloads, and can be deployed securely with Entra authentication.
      10 npm
      MIT

    • pdf-mcp

      saury1120
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables PDF document processing including text, image, and table extraction, as well as intelligent classification and similarity analysis across multiple languages.
      51
      MIT

    • ParseFlow MCP Server

      Libres-coder
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to parse and search documents including PDF, Word, Excel, PowerPoint, and images via OCR, with support for semantic search and batch processing.
      2
      MIT

    • doc-cheap

      cheap-doc
      A
      license
      A
      quality
      B
      maintenance
      Reads passports, ID cards and driver's licences from a photo or scan and returns the printed fields and MRZ as structured JSON. One credit ($0.01) per recognised document; nothing is charged when no document is found.
      6
      222 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.6/5.0

    Scored across 2 tools

    Disambiguation1/5

    The two tools have nearly identical purposes: both use Azure Form Recognizer to extract structured data from documents/forms. 'analyze-document' and 'extract-form-data' are functionally indistinguishable, with no clear boundary between them. This high ambiguity will cause agents to misselect between tools.

    Naming Consistency3/5

    Both tools use kebab-case naming, which is consistent. However, the verb choices ('analyze' vs 'extract') are different despite similar functionality, creating minor inconsistency. The naming pattern is readable but not perfectly aligned in purpose.

    Tool Count2/5

    With only 2 tools, the server feels thin for a vision/document processing domain. A typical MCP server for this scope would include more operations like text extraction, image analysis, or OCR configuration. The minimal tool count limits functionality and suggests incomplete coverage.

    Completeness2/5

    For a vision/document processing server, there are significant gaps: no image analysis tools, no OCR configuration, no batch processing, and no support for different document types beyond forms. The surface is severely limited, focusing only on form data extraction without broader vision capabilities.

    Resources