io.github.nauman/builtonrails

Est-ce que io.github.nauman/builtonrails est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.nauman/builtonrails » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 18 outils

• admin_changelog≈ 412 tokens

  ADMIN ONLY - the feature/changelog ledger over MCP. Requires an admin Bearer token. This is the source of truth for what shipped - log an entry here right after shipping something instead of hand-editing docs/changelog.md, so the record can't drift from reality. Entries left un-digested automatically get folded into the next Monday promotional digest (see admin_newsletters). Actions: 'list' shows recent entries (filter by category or digest status); 'create' logs a new entry (title, description, category, optional version); 'update' edits an entry by id; 'destroy' removes one.

  Paramètres, retour & exemple (7)

  Paramètres

  • id · integer · optionnel
    Entry id - required for update/destroy
  • title · string · optionnel
    create/update: short headline
  • action · string · requis · list | create | update | destroy
    list | create | update | destroy
  • version · string · optionnel
    create/update: e.g. '6.11.0' (optional)
  • category · string · optionnel · added | changed | fixed | improved
    create/update: added | changed | fixed | improved
  • description · string · optionnel
    create/update: the technical detail
  • pending_only · boolean · optionnel
    list: only entries not yet included in a digest

  Exemple d'appel

  {"name": "admin_changelog", "arguments": {"action": "list"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• admin_moderation≈ 272 tokens

  ADMIN ONLY - moderate BuiltOnRails listings over MCP. Requires an admin Bearer token (Authorization header). Actions: 'pending' lists products awaiting review; 'approve' / 'reject' run the review lifecycle on a product slug; 'feature' / 'unfeature' toggle homepage featuring; 'stats' returns moderation counts. Params: action (required); slug (required for approve/reject/feature/unfeature); limit (pending only, default 10, max 50).

  Paramètres, retour & exemple (3)

  Paramètres

  • slug · string · optionnel
    Product slug — required for approve/reject/feature/unfeature
  • limit · integer · optionnel
    Max results for 'pending' (default 10, max 50)
  • action · string · requis · pending | approve | reject | feature | unfeature | stats
    One of: pending, approve, reject, feature, unfeature, stats

  Exemple d'appel

  {"name": "admin_moderation", "arguments": {"action": "pending"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• admin_news≈ 309 tokens

  ADMIN ONLY - batch-review the curated news queue (ContentItems behind /daily and the newsletter) over MCP. Requires an admin Bearer token. Actions: 'queue' lists items awaiting review (filter by feed name or search term); 'select' / 'reject' batch-review by ids (array); 'stats' returns queue counts by status and top feeds. Typical flow: queue -> read titles -> select the good ids, reject the noise, in batches.

  Paramètres, retour & exemple (5)

  Paramètres

  • ids · array · optionnel
    ContentItem ids - required for select/reject (max 100 per call)
  • feed · string · optionnel
    queue: filter by content feed name (partial match)
  • limit · integer · optionnel
    queue: max results (default 25, max 50)
  • query · string · optionnel
    queue: search term matched against title
  • action · string · requis · queue | select | reject | stats
    queue | select | reject | stats

  Exemple d'appel

  {"name": "admin_news", "arguments": {"action": "queue"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• admin_newsletters≈ 530 tokens

  ADMIN ONLY - queue and send promotional/update newsletters over MCP. Requires an admin Bearer token. Each newsletter is only ever delivered once per subscriber, even across retries. The 'all_subscribed' segment is additionally throttled: it skips anyone who got a newsletter in the last 7 days or any email at all in the last 2 days, so promos never stack on top of other mail. Leaving an 'all_subscribed' newsletter as a draft (don't call send_now) queues it for the automatic weekly digest every Monday 10am, which folds all pending drafts into one combined email instead of several separate sends. Actions: 'list' shows recent newsletters with status and segment; 'segments' returns live, throttle-aware recipient counts for each segment so you can preview reach before sending; 'pending_digest' lists drafts currently queued for next Monday's digest; 'create' drafts a newsletter (subject, content, segment); 'update' edits a draft/scheduled newsletter's fields; 'send_now' sends immediately in the background instead of waiting for the digest; 'destroy' deletes a newsletter.

  Paramètres, retour & exemple (5)

  Paramètres

  • id · integer · optionnel
    Newsletter id - required for update/send_now/destroy
  • action · string · requis · list | segments | pending_digest | create | update | send_now | destroy
    list | segments | pending_digest | create | update | send_now | destroy
  • content · string · optionnel
    create/update: body, plain text or markdown
  • segment · string · optionnel · inactive | all_subscribed
    create/update: 'inactive' (re-engage users quiet 14+ days) or 'all_subscribed' (promotional blast to everyone opted into the newsletter). Defaults to 'inactive'.
  • subject · string · optionnel
    create/update: email subject line

  Exemple d'appel

  {"name": "admin_newsletters", "arguments": {"action": "list"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• admin_sponsors≈ 526 tokens

  ADMIN ONLY - manage site sponsors over MCP. Requires an admin Bearer token. Actions: 'list' shows sponsors with performance (impressions, clicks, CTR, running state); 'create' adds a manual sponsor (name, url, position, optional tagline/dates); 'update' changes fields on a sponsor by id; 'activate' / 'deactivate' toggle a sponsor; 'inquiries' lists sponsorship inquiries; 'inquiry_status' moves an inquiry through pending -> contacted -> converted/declined; 'orders' lists self-serve sponsor orders.

  Paramètres, retour & exemple (10)

  Paramètres

  • id · integer · optionnel
    Sponsor id (update/activate/deactivate) or inquiry id (inquiry_status)
  • url · string · optionnel
    create/update: sponsor link URL
  • name · string · optionnel
    create/update: sponsor name
  • action · string · requis · list | create | update | activate | deactivate | inquiries | inquiry_status | orders
    list | create | update | activate | deactivate | inquiries | inquiry_status | orders
  • status · string · optionnel · pending | contacted | converted | declined
    inquiry_status: pending | contacted | converted | declined
  • ends_at · string · optionnel
    create/update: end date, YYYY-MM-DD (omit = open-ended)
  • tagline · string · optionnel
    create/update: short tagline shown on the ad
  • cta_text · string · optionnel
    create/update: call-to-action label (default 'Learn More')
  • position · string · optionnel · sidebar | banner | featured
    create/update: sidebar | banner | featured
  • starts_at · string · optionnel
    create/update: start date, YYYY-MM-DD (omit = immediately)

  Exemple d'appel

  {"name": "admin_sponsors", "arguments": {"action": "list"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• compare_stacks≈ 161 tokens

  Compare two technology stacks head-to-head with real adoption data. Returns products count, GitHub stars, collections, growth trends, and a winner. Uses the same scoring algorithm as the BuiltOnRails Stack Showdown feature.

  Paramètres, retour & exemple (2)

  Paramètres

  • stack1 · string · requis
    First stack name (e.g. 'Sidekiq')
  • stack2 · string · requis
    Second stack name (e.g. 'Solid Queue')

  Exemple d'appel

  {"name": "compare_stacks", "arguments": {"stack1": "texte", "stack2": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• detect_stacks≈ 220 tokens

  Detect technology stacks from a Gemfile, gemspec, package.json, or importmap.rb content. Paste your dependency file content and get back matched stacks with real adoption data. The killer feature for coding agents — understand your project's stack landscape instantly.

  Paramètres, retour & exemple (4)

  Paramètres

  • gemfile · string · optionnel
    Raw Gemfile content
  • gemspec · string · optionnel
    Raw .gemspec content — gems declare deps here, not in the Gemfile
  • importmap · string · optionnel
    Raw config/importmap.rb content
  • package_json · string · optionnel
    Raw package.json content

  Exemple d'appel

  {"name": "detect_stacks", "arguments": {"gemfile": "texte", "gemspec": "texte", "importmap": "texte", "package_json": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_categories≈ 90 tokens

  Get all available stack categories with descriptions and stack counts. Useful for understanding what types of technologies are tracked and filtering searches.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_categories", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_collection≈ 143 tokens

  Get a curated stack collection by slug. Collections are hand-picked sets of technology stacks with notes and optional LLM prompts for AI context. Returns the collection with all stacks in order, notes, and the LLM prompt if available.

  Paramètres, retour & exemple (1)

  Paramètres

  • slug · string · requis
    Collection slug (e.g. 'modern-rails-2024', 'essential-saas-stack')

  Exemple d'appel

  {"name": "get_collection", "arguments": {"slug": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_news≈ 254 tokens

  Read curated Rails ecosystem news and articles - the same pipeline behind builtonrails.com/daily. Returns recent items (title, url, summary, category, source). Filter by category (article, release, podcast, video, news), a specific date (YYYY-MM-DD), or a search term. Use this for 'what's new in Rails', release announcements, and article discovery.

  Paramètres, retour & exemple (4)

  Paramètres

  • date · string · optionnel
    Specific day, YYYY-MM-DD
  • limit · integer · optionnel
    Max results (default 15, max 50)
  • query · string · optionnel
    Search term matched against title and summary
  • category · string · optionnel · article | release | podcast | video | news
    Filter: article, release, podcast, video, news

  Exemple d'appel

  {"name": "get_news", "arguments": {"date": "texte", "limit": 1, "query": "texte", "category": "article"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_product≈ 118 tokens

  Get detailed information about a specific production Rails application. Returns full product details including description, tags, member, stacks, and vote count.

  Paramètres, retour & exemple (1)

  Paramètres

  • slug · string · requis
    Product slug (e.g. 'shopify', 'hey', 'github')

  Exemple d'appel

  {"name": "get_product", "arguments": {"slug": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_products_using_stacks≈ 195 tokens

  Find real Rails applications that use specific technology stacks. Returns approved products using ALL specified stacks, with their full stack lists and vote counts. Great for finding real-world examples of specific tech stack combinations.

  Paramètres, retour & exemple (2)

  Paramètres

  • limit · integer · optionnel
    Maximum number of products to return (default: 10, max: 25)
  • stacks · array · requis
    Stack names to search for (e.g. ['PostgreSQL', 'Sidekiq']). Returns products using ALL specified stacks.

  Exemple d'appel

  {"name": "get_products_using_stacks", "arguments": {"stacks": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_stack_recommendations≈ 228 tokens

  Get stack recommendations based on what real Rails apps use together. Given your current stacks, recommends the most popular stacks in a target category based on co-occurrence in production Rails applications. Available categories: Framework, Database, Frontend, Background, Search, Auth, Payments, DevOps, Testing, Analytics, LLM, AI/ML, Observability, Security, Email.

  Paramètres, retour & exemple (2)

  Paramètres

  • category · string · requis
    Category to get recommendations for (e.g. 'Background', 'Auth', 'Testing')
  • current_stacks · array · requis
    Your current stacks (e.g. ['PostgreSQL', 'Hotwire', 'Tailwind CSS'])

  Exemple d'appel

  {"name": "get_stack_recommendations", "arguments": {"category": "texte", "current_stacks": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_stack_trends≈ 168 tokens

  Get adoption trend data for a technology stack over time. Returns historical usage snapshots showing how many Rails apps use the stack, plus growth percentage. Useful for understanding if a stack is growing or declining.

  Paramètres, retour & exemple (2)

  Paramètres

  • days · integer · optionnel
    Number of days of trend data (default: 90, max: 365)
  • stack_name · string · requis
    Stack name (e.g. 'Solid Queue', 'Sidekiq')

  Exemple d'appel

  {"name": "get_stack_trends", "arguments": {"stack_name": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• my_product≈ 557 tokens

  OWNERS ONLY - manage your own products over MCP. Requires a write-scope Bearer token; you can only touch products you submitted or founded. Actions: 'list' shows your products; 'update' edits fields on one of your products (description, url, product_type, tags, github_repo_path); 'post_update' publishes a product update (title + update_type, optional content/url/version) shown on your product page; 'updates' lists a product's recent updates. Params: action (required); slug (required except for 'list').

  Paramètres, retour & exemple (11)

  Paramètres

  • url · string · optionnel
    update: new product URL / post_update: link for the update
  • slug · string · optionnel
    Product slug — required for update/post_update/updates
  • tags · array · optionnel
    update: replace product tags
  • title · string · optionnel
    post_update: update title (required for post_update)
  • action · string · requis · list | update | post_update | updates
    One of: list, update, post_update, updates
  • content · string · optionnel
    post_update: update body (markdown, max 10k chars)
  • version · string · optionnel
    post_update: version string for 'release' updates (e.g. '2.1.0')
  • description · string · optionnel
    update: new product description
  • update_type · string · optionnel · release | update | feature | blog | video | announcement | milestone | listing
    post_update: release, update, feature, blog, video, announcement, milestone, listing, episode, issue
  • product_type · string · optionnel
    update: SaaS, Gem, Open Source, Marketplace, Tool, Platform, Agency, Studio
  • github_repo_path · string · optionnel
    update: GitHub repo path (e.g. 'rails/rails')

  Exemple d'appel

  {"name": "my_product", "arguments": {"action": "list"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• search_products≈ 227 tokens

  Search real production Rails applications and the stacks they actually run. Returns approved products with name, URL, type, votes, and stacks. Filter by product type or sort by votes/newest.

  Paramètres, retour & exemple (4)

  Paramètres

  • sort · string · optionnel · votes | newest
    Sort order: 'votes' (most upvoted) or 'newest' (default)
  • type · string · optionnel
    Filter by product type (e.g. 'SaaS', 'Gem', 'Open Source', 'Marketplace')
  • limit · integer · optionnel
    Max results (default: 10, max: 25)
  • query · string · optionnel
    Search term to match product name (e.g. 'shopify', 'hey')

  Exemple d'appel

  {"name": "search_products", "arguments": {"sort": "votes", "type": "texte", "limit": 1, "query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• search_stacks≈ 223 tokens

  Search for technology stacks (gems, frameworks, services) used by Rails applications. Returns matching stacks with real adoption data including product counts, GitHub stars, and category. Available categories: Framework, Database, Frontend, Background, Search, Auth, Payments, DevOps, Testing, Analytics, LLM, AI/ML, Observability, Security, Email.

  Paramètres, retour & exemple (2)

  Paramètres

  • query · string · requis
    Search term (e.g. 'sidekiq', 'auth', 'postgres')
  • category · string · optionnel
    Filter by category: Framework, Database, Frontend, Background, Search, Auth, Payments, DevOps, Testing, Analytics, LLM, AI/ML, Observability, Security, Email

  Exemple d'appel

  {"name": "search_stacks", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• submit_product≈ 383 tokens

  Add a Rails application to BuiltOnRails so its stack becomes part of the data. The product is created with 'pending' status and goes through admin approval. Attach stacks by name, or paste your Gemfile / package.json / importmap.rb content and the real stack is detected and attached automatically - the recommended path.

  Paramètres, retour & exemple (8)

  Paramètres

  • url · string · requis
    Product website URL (e.g. 'https://shopify.com')
  • name · string · requis
    Product name (e.g. 'Shopify')
  • stacks · array · optionnel
    Stack names to associate (e.g. ['PostgreSQL', 'Sidekiq'])
  • gemfile · string · optionnel
    Raw Gemfile content - stacks are auto-detected and attached
  • importmap · string · optionnel
    Raw config/importmap.rb content - stacks are auto-detected and attached
  • description · string · requis
    Short description of the product
  • package_json · string · optionnel
    Raw package.json content - stacks are auto-detected and attached
  • product_type · string · optionnel
    Type: SaaS, Gem, Open Source, Marketplace, Tool, Platform, Agency, Studio

  Exemple d'appel

  {"name": "submit_product", "arguments": {"url": "texte", "name": "texte", "description": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://builtonrails.com/mcp/sse